Implements parts of:
- P0355 Extending chrono to Calendars and Time Zones

Static verifier reports unchecked use of pointer after explicitly
checking earlier in the function. It appears the pointer won't be a
nullptr, so remove the unneeded check for consistency.

Part of #93566.

When the integer range analysis was first develop, a pass that did
integer range-based constant folding was developed and used as a test
pass. There was an intent to add such a folding to SCCP, but that hasn't
happened.

Meanwhile, -int-range-optimizations was added to the arith dialect's
transformations. The cmpi simplification in that pass is a strict subset
of the constant folding that lived in
-test-int-range-inference.

This commit moves the former test pass into -int-range-optimizaitons,
subsuming its previous contents. It also adds an optimization from
rocMLIR where `rem{s,u}i` operations that are noops are replaced by
their left operands.

The different build configuration and target Linux system can load a
different number of .so libraries. Add and check own libraries. 

The test clang/test/OpenMP/error_unsupport_feature.c don't check the
output written to the current directory. The current directory may be
write protected e.g. in a sandboxed environment.

This patch replace the -emit-llvm option with -emit-llvm-only as it
don't care about the outputed llvm IR.

close: #92538

Just use the original type and let it hit a standard legalization error.

We can't use `dladdr()` in the tests, because when we're statically
linking with musl that function is a no-op.

Additionally, because musl disables emission of unwind information in
its build, and because its signal trampolines don't include unwind
information, tests that involve unwinding through a signal handler won't
work and need to be disabled for musl.

rdar://123436891

See Buildbot failures:

- https://lab.llvm.org/buildbot/#/builders/257/builds/13450
- https://lab.llvm.org/buildbot/#/builders/256/builds/14531

Since inreg now works for the default calling convention, we can
check the output with fewer argument shuffling instructions.

This was probably intended to test the immediate offset addressing
mode. Add some tests to check immediate offsets, and clean up run lines.

Related review: https://github.com/llvm/llvm-project/pull/91724

This patch updates the RemoveDIs migration document to include details
on the textual IR changes, including steps to update any downstream lit
tests accordingly. These steps are the same as those used to update the
lit tests in the LLVM/Clang lit tests, as detailed in the review linked
above.

Reverts llvm/llvm-project#94212
Some codes assume that `NDEBUG` implies
`LLVM_ENABLE_ABI_BREAKING_CHECKS`, thus #94212 breaks some build bots.

Otherwise these tests would fail when using gnuwin32.

Revert 291b415c : [Misc] Use `LLVM_ENABLE_ABI_BREAKING_CHECKS` correctly (#94212)

The patch didn't consistently clean up `#ifdef LLVM_ENABLE_ABI_BREAKING_CHECKS` and '#if defined(LLVM_ENABLE_ABI_BREAKING_CHECKS)' paths, causing a lot of build failures

nvcc warns about the following code:

`void f();
__device__ void f() {}`

but clang does not since clang allows device function to overload host
function.

Users want clang to emit similar warning to help code to be compatible
with nvcc.

Since this may cause regression with existing code, the warning is off
by default and can be enabled by -Wnvcc-compat.

It won't cause warning in system headers, even with -Wnvcc-compat.

After enhancing MSVC's STL to statically initialize our condition_variable,
Clang began noticing that some mutexes in the test suite were unused.

Introduced by 2cf14398 (#94279).
See also 6c369cf9.
The build system cannot track transitive dependencies on generated
headers for some reason.

These will work as AST Text node dumpers, as usual, instead of AST
printers.

Note that for now, the TemplateName dumper is using the TemplateArgument
dumper through an implicit conversion.
This can be fixed in a later pass.

The categories are primarily meant for OpenMP, where the spec assigns a
category to each directive. It's one of declarative, executable,
informational, meta, subsidiary, and utility.

These will be used in clang to avoid listing directives belonging to
certain categories by hand.

---------

Co-authored-by: Valentin Clement (バレンタイン クレメン) <clementval@gmail.com>

The dependency expansion step which was introduced by FMV has been
erroneously used for non-FMV features, for example when parsing the
target attribute. The PR #93695 has rectified most of the tests which
were relying on dependency expansion of target features specified on the
-cc1 command line. In this patch I am decoupling the dependency
expansion of features specified on the target attribute from FMV.

To do that first I am expanding FMV dependencies before passing the list
of target features to initFeatureMap(). Similarly when parsing the
target attribute I am reconstructing an ExtensionSet from the list of
target features which was created during the command line option
parsing. The attribute parsing may toggle bits of that ExtensionSet and
at the end it is converted to a list of target features. Those are
passed to initFeatureMap(), which no longer requires an override.

A side effect of this refactoring is that features specified on the
target_version attribute now supersede the command line options, which
is what should be happening in the first place.

See Buildbot failure:
https://lab.llvm.org/buildbot/#/builders/138/builds/67428.

There is no test for this code and it also do not change the result of
https://github.com/dtcxzyw/llvm-opt-benchmark when I run it locally.
I have not been able to make a test for this and do not know how to
handle the range attribute for this so maybe it shall be removed?

Part of #93566.

/llvm-project/llvm/lib/Target/AMDGPU/AMDGPUAsmPrinter.cpp:653:13:
error: unused variable 'PGMRSrc3' [-Werror,-Wunused-variable]
    int64_t PGMRSrc3;
            ^
1 error generated.

`LLVM_ENABLE_ABI_BREAKING_CHECKS` is always defined:

https://github.com/llvm/llvm-project/blob/72c901f5e59477e568b1b04dae9de753b9d1f6f3/llvm/include/llvm/Config/abi-breaking.h.cmake#L16C2-L16C15
It uses `cmakedefine01` rather than `cmakedefine`, so
`LLVM_ENABLE_ABI_BREAKING_CHECKS` is always defined,
so the preprocessed code is probably not what the author wanted.

The recently landed commit c5aeca73 causes debug records to be used by
default; while this mostly has no direct effect on output, one side
effect is that intrinsics are deleted and recreated in memory, which
can change certain properties. This broke a test that expected `tail`
to be set on some debug intrinsics; as this property has no effect on
debug intrinsics, this patch removes the expectation.

Committed without review due to being a trivial test update; if this
needs discussion, see review:
  https://github.com/llvm/llvm-project/pull/89799

Add extra test coverage to ensure decisions do not change when
transitioning to a VPlan-based cost model.

Reapplies commit 91446e2a, which was reverted due to a downstream error,
discussed on the pull request. The error could not be reproduced
upstream, and cannot be reproduced downstream as-of current main, so
until the error can be confirmed to still exist this patch should
return.

This reverts commit 23f8fac7.

Context: https://github.com/llvm/llvm-project/pull/94568/files#r1631349423

- Reintroduce the RefinePositionToZero path in the unittest.
- Adjust some inline function argument hints to match the same style.

This reverts commit 760d880e.

It broke https://lab.llvm.org/buildbot/#/builders/169/builds/32309

Eliminates assumption that MCExpr comments/remarks being emitted are
always resolvable

They have been superseded by llvm.amdgcn.raw.buffer.* and
llvm.amdgcn.struct.buffer.*.