These tests just don't check the output written to the current directory. The
current directory may be write protected e.g. in a sandboxed environment.

The Testcases that use -emit-llvm and -verify only care about stdout/stderr
and are in this patch changed to use -emit-llvm-only to avoid writing to an
output file. The verify-inlineasmbr.mir testcase that also only care about
stdout/stderr is in this patch changed to throw away the output file and just
write to /dev/null.

`TemplateArgumentLocInventIterator` default constructor should not
exists

https://github.com/llvm/llvm-project/blob/3496927edcd0685807351ba88a7e2cfb006e1c0d/clang/lib/Sema/TreeTransform.h#L4742
because it doesn't and couldn't initialize `Self` member that is
reference:

https://github.com/llvm/llvm-project/blob/3496927edcd0685807351ba88a7e2cfb006e1c0d/clang/lib/Sema/TreeTransform.h#L4721-L4723

Instantiation of this constructor is always a compile-time error. 

Please note, that I didn't run any tests, because cannot imagine
situation where this constructor can be properly used. There are no new
tests for this fix for the same reason.

The new name uses experimental which better conveys what it means.

[clang] Marshallers.h - use move semantics for 'NodeKinds' and update possible callers to use it  (#87273)

Fixes: https://github.com/llvm/llvm-project/issues/87248



Signed-off-by: amila <amila.15@cse.mrt.ac.lk>

This implements two kinds of optimizations. Specifically
- `char_traits<char8_t>` uses `char` code paths; these are heavily
  optimized and the operations are equivalent
- `char16_t` and `char32_t` `find` uses `std::find` to forward to
  `wmemchr` if they have the same size

Resolve #85250 
Alive2: https://alive2.llvm.org/ce/z/7DMRCy

Also fix a bug in annotating TrailingAnnotation.

Closes #61233.

Matches up with the clang setting

Lambda without trailing auto could have return type declared inside the
body too.

Fixes #68775

Avoid passing them around.

They are not optional.

This reverts commit 2dfa30d0.

This relands commit 0a6c74e2.

This patch originally caused a host of buildbot failures due to several
buildbots not having the necessary python version. That was tracked in
issue #83962, and all bots that failed in the first round have now been
updated. This is an attempt to reland the patch to see if it sticks or
if there are a number of long-running bots where this patch will cause
failures.

Reverts llvm/llvm-project#89378

Broke the windows premerge checks
https://lab.llvm.org/buildbot/#/builders/271/builds/6788

This reverts commit 2a632d3d.

This has some implication on OpenACC postDeallocate action

We have a lot of repeated code with random constants.
Particular values are not important, the one just needs to be
bigger then another.

UR_NONTAKEN_WEIGHT is selected as it's the most common one.

It reduces instrumentation overhead by ~50%.

OnDiskIterableChainedHashTable::Create can default-contruct a trait
object for us.  We don't need to construct one on our own unless we
need to customize something (like a version number).

This adds a hint to the missing symbols error message to make it easier
to understand what this means to users.

[Reapplies an earlier patch with a test fix.]

This reverts commit 08163cd9.

I accidentally broke the test while addressing review feedback.

Prepare for #89458

Remove hardcode GENERIC cpu from RISCVTargetDefEmitter.cpp.

Assumed size arrays are apparently allowed with attribute device.

Add baseline tests which should comprehensively test the new atomic
metadata. Test codegen / expansion, and preservation in a few
transforms.

New metadata defined in #85052

When the STREAM option is specified on an ALLOCATE statement, the object
must have the DEVICE attribute.

When the PINNED option is specified on an ALLOCATE statement, the object
must have the PINNED attribute.

Automatic deallocation of allocatable that are cuda device variable must
use the fir.cuda_deallocate operation. This patch update the automatic
deallocation code generation to use this operation when the variable is
a cuda variable.

Only FieldDecls are of importance here. A struct defined within another
struct has the same semantics as if it were defined outside of the
struct. So there's no need to look into RecordDecls that aren't a field.

This copies MSVC behavior, and avoids weird link errors in certain
cases.

Run `modernize-use-starts-ends-with` on llvm-project. Two instances are
flagged, minor readability improvements, extremely minor performance
improvements.

```
python3 clang-tools-extra/clang-tidy/tool/run-clang-tidy.py \
    -clang-tidy-binary="build/bin/clang-tidy" \
    -clang-apply-replacements-binary="build/bin/clang-apply-replacements" \
    -checks="-*,modernize-use-starts-ends-with" \
    -header-filter=".*" \
    -fix -format
```

I am working on some additions to this check, but they don't seem to
flag any additional cases anyway.

This adds a hint to the missing symbols error message to make it easier
to understand what this means to users.