There is a minor behavior difference that is not worth testing for the obsoleted
format. Previously, llvm-dwarfdump considers .zdebug_info as a debug section but
does not decompress it, leading to a warning when the content cannot be parsed.
Now llvm-dwarfdump just ignores the section without a warning.

type_traits is currently unable to include __type_traits/noexcept_move_assign_container.h, because it would cause several include cycles.

type_traits -> __type_traits/noexcept_move_assign_container.h -> __memory/allocator_traits.h -> __memory/construct_at.h -> new -> exception -> type_traits

type_traits -> __type_traits/noexcept_move_assign_container.h -> __memory/allocator_traits.h -> __memory/construct_at.h -> new -> type_traits

type_traits -> __type_traits/noexcept_move_assign_container.h -> __memory/allocator_traits.h -> limits -> type_traits

This is a problem for clang modules after the std mega module is broken up (D144322), because it becomes a module cycle which is a hard error.

Unconditionally remove the type_traits includes from limits and new in all versions, and also remove the exception include from new. (These are already removed in C++23.)

Reviewed By: ldionne, Mordante, #libc

Differential Revision: https://reviews.llvm.org/D153214

D106624 added a .dwo warning (when there are relocations) that may fire for
non-debug sections, e.g. `.rodata.dwo` when there is a data symbol foo in
-fdata-sections mode. Adjust it to only warn for .debug sections.

While here, change the diagnostic to be more conventional
https://llvm.org/docs/CodingStandards.html#error-and-warning-messages and use
the relocated section name instead of the relocation section name.

This change does not handle `.zdebug` (support was mostly removed from LLVM) or
`__debug` (Mach-O, no DWO support).

Reviewed By: ayermolo, HaohaiWen

Differential Revision: https://reviews.llvm.org/D153602

Fix build error caused by D153679

Reviewed By: nikic

Differential Revision: https://reviews.llvm.org/D153704

Reviewed By: #libc, Mordante

Differential Revision: https://reviews.llvm.org/D153427

Reviewed By: RKSimon

Differential Revision: https://reviews.llvm.org/D153684

Addresses:  LWG3719 - Directory iterators should be usable with default sentinel
https://wg21.link/LWG3719

Reviewed By: #libc, Mordante

Differential Revision: https://reviews.llvm.org/D153299

A nested class in a member function can erroneously confuse the check into
thinking that any CXXThisExpr found relate to the outer class, preventing any warnings.
Fix this by not traversing any nested classes.

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

Reviewed By: PiotrZSL

Differential Revision: https://reviews.llvm.org/D130665

The last use was removed by:

  commit 7d894374
  Author: OCHyams <orlando.hyams@sony.com>
  Date:   Thu Mar 16 08:48:36 2023 +0000

The last uses were removed by:

  commit 79b3f082
  Author: Tim Northover <tnorthover@apple.com>
  Date:   Tue Feb 7 11:28:00 2023 +0000

Differential Revision: https://reviews.llvm.org/D153679

Differential Revision: https://reviews.llvm.org/D153678

The last use was removed by:

  commit 73523021
  Author: Chandler Carruth <chandlerc@gmail.com>
  Date:   Mon Jan 13 13:07:17 2014 +0000

The last use was removed by:

  commit 243acd5d
  Author: Nikita Popov <npopov@redhat.com>
  Date:   Fri Dec 9 15:29:35 2022 +0100

The last use was removed by:

  commit 2d79b713
  Author: Philip Reames <preames@rivosinc.com>
  Date:   Thu Apr 6 08:23:08 2023 -0700

The last use was removed by:

  commit f9b523eb
  Author: Kazu Hirata <kazu@google.com>
  Date:   Wed May 31 07:30:14 2023 -0700

Check detects cyclic #include dependencies between user-defined headers.

Reviewed By: njames93

Differential Revision: https://reviews.llvm.org/D144828

Following what is already performed for vector.reduce.fmin/fmax, this adds
lowering for the new vector.reduce.fminimum/fmaximum nodes to the SVE fminv
and fmaxv instructions via the existing FMINV_PRED/FMAXV_PRED nodes.

Differential Revision: https://reviews.llvm.org/D153288

This reverts commit f3aa6cc0.

Check detects cyclic #include dependencies between user-defined headers.

Reviewed By: njames93

Differential Revision: https://reviews.llvm.org/D144828

It has been reported to that the current clang  errors for, specifically,
static_assert in export contexts are a serious blocker to adoption of
modules in some cases.

There is also implementation divergence with GCC and MSVC allowing the
constructs mentioned below where clang currently rejects them with an
error.

The category of errors [for declarations in an exported context] is:
(unnamed, static_assert, empty and asm decls). These are now permitted
after P2615R1 which was approved by WG21 as a DR (and thus should be
applied to C++20 as well).

This patch removes these diagnostics and amends the testsuite accordingly.

Differential Revision: https://reviews.llvm.org/D152946

These functions have been deprecated since:

  commit ec116ea6
  Author: Kazu Hirata <kazu@google.com>
  Date:   Sun Feb 12 12:11:51 2023 -0800

Differential Revision: https://reviews.llvm.org/D153686

Add -fcheck-new and -fno-check-new, from GCC, which make the compiler
not assume pointers returned from operator new are non-null.
Fixes #16931.

Reviewed By: MaskRay

Differential Revision: https://reviews.llvm.org/D125272

We expect log messages from enother thread triggered by actions.

Reviewed By: arsenm

Differential Revision: https://reviews.llvm.org/D153643

This is just a cleanup commit, a follow up will make this way more
structured.

We now consistently use `CallBase::getCalledOperand` rather than
`getCalledFunction`, as we do not want the type checked performed by the
latter. This exposed various missing checks to handle mismatches
properly, but it is good to have them explicit now.

In a follow up we might want to flag certain calls as UB, but for now,
we allow everything to cut down on unexpected differences.

Partial progress towards replacing in-tree uses of
`Type::getPointerTo()`.

If `getPointerTo()` is used solely to support an unnecessary bitcast,
remove the bitcast.

Reviewed By: barannikov88, nikic

Differential Revision: https://reviews.llvm.org/D153307

When initializing DialectInterfaceCollection, we wouldn't have the missing
interface name in the error.

Differential Revision: https://reviews.llvm.org/D153676

These aren't detected during testing most of the time because the way we
are setting up mlir-opt and the fact that we always use func.func: it'll
trigger the load of the InlinerInterface extension for the FuncDialect which
itself loads these dialects unconditionally.

[LegacyPM] Remove unused declarations createLowerMatrixIntrinsicsPass and createLowerMatrixIntrinsicsMinimalPass

The corresponding function definitions were removed by:

  commit 27643229
  Author: Kazu Hirata <kazu@google.com>
  Date:   Fri Jun 23 01:32:38 2023 -0700

The corresponding function definition was removed by:

  commit 15977742
  Author: Arthur Eubanks <aeubanks@google.com>
  Date:   Tue Dec 20 13:36:20 2022 -0800

The corresponding function definitions were removed by:

  commit c8b8d6ba
  Author: Arthur Eubanks <aeubanks@google.com>
  Date:   Thu Feb 9 17:22:56 2023 -0800

[LegacyPM] Remove unused declarations initializeCorrelatedValuePropagationPass and initializeJumpThreadingPass

The corresponding function definitions were removed by:

  commit 7c3c9814
  Author: Arthur Eubanks <aeubanks@google.com>
  Date:   Wed Mar 8 15:07:17 2023 -0800