[OCaml] Add FMaximumNum and FMinimumNum to AtomicRMWBinOp.t (#240894)
`LLVMAtomicRMWBinOp` gained `LLVMAtomicRMWBinOpFMaximumNum` and
`LLVMAtomicRMWBinOpFMinimumNum`, but the OCaml variant
`AtomicRMWBinOp.t` stops at `FMinimum`, so OCaml code cannot build these
operations. `build_atomicrmw` passes the constructor index straight to
`LLVMBuildAtomicRMW`, so the two lists have to stay in the same order.
This adds the two constructors at the end of the variant, in the C
order.
Assisted-by: Mistral Vibe
[clang-format] Break and align items after trailing-comma __VA_OPT__ (#240902)
When `__VA_OPT__(..., )` (or `__VA_OPT__(,)`) ends with a top-level
comma inside an enum, braced list, parameter list, or expression (for
example when migrating unnamed variadic macros from the non-standard `,
##__VA_ARGS__` extension to C++20 `__VA_OPT__(__VA_ARGS__, )`), its
closing `)` acts as an item separator. Previously, `clang-format` did
not recognize the trailing comma inside `__VA_OPT__`, keeping the
following item on the same line (or continuation-indenting it after
`)`).
Classify the closing `)` of a C/C++ `__VA_OPT__` ending in a top-level
non-operator comma as `TT_TrailingCommaVaOptRParen` and treat it as a
comma separator across token annotation, parameter counting and column
layout, bin-packing, continuation indentation, trailing-comma handling,
and expression grouping.
Before:
[21 lines not shown]
[libc] Add strtof128 stdlib entrypoint. (#243955)
Enable for aarch64, riscv, and x86_64, using the emulated float128 type
in the implementation and helper tests.
The logic for string to float128 conversion is already in
__support/str_to_float.h for the case when long double is quad
precision. It just needed some template updates to enable for float128.
Assisted-by: Automated tooling, human reviewed.
[VPlan] Remove unused VPLane::getKnownLane (NFC) (#244312)
The last callers were removed on November 19, 2026 in commit
39cc2f5728e49e5c8df0acd80fd17985862df9d3.
Assisted-by: Antigravity
[AMDGPU] Remove unused getGPUName and getFeatureString (NFC) (#244311)
The last callers were removed on November 18, 2026 in commit
95f23a1ae335e929987a99521ab7e3e08da54ba4.
Assisted-by: Antigravity
[IR] Remove unused RuntimeLibcallsInfo::darwinHasSinCosStret (NFC) (#244307)
The last caller was removed on November 18, 2026 in commit
3490218b05171319625693a1c0003dbb793a0e76.
Assisted-by: Antigravity
[TableGen] Remove unused InfoByHwMode::makeSimple (NFC) (#244306)
The last caller was removed on November 6, 2026 in commit
7d2b3c904c95f7173b677f6d04eb8fff0c8932b7.
Assisted-by: Antigravity
[llvm][vfs] Add Status::isExecutable() (#244339)
Add a query to vfs::Status that returns whether any of the execute
permissions is set, so that clients checking whether a file found
through a VFS is executable don't have to test the permission bits by
hand. Update MSVC toolchain to use the new API.
Unlike sys::fs::can_execute, it does not check whether the current
process is allowed to execute the file.
[lldb] Add a Deprecated attribute for settings, to discourage use (#243732)
I want to change all of the lldb-cache-index settings that exist today,
reorganizing them to reflect how I'm growing the DataFileCache system.
Users may have the old settings in their .lldbinit files, and I don't
want those to result in errors. I will mark the old settings Deprecated,
and if they are set, have them set the correct new setting names.
The goal of a deprecated setting is to make it undiscoverable by
accident -- `settings list`, `settings show` will not show the name
unless the full path is given, unless `--include-deprecated` is added.
When it is shown, the setting name will be followed by a deprecation
tag, "(deprecated)". If a user sets a setting with `settings set`, a
warning will be printed that this setting is deprecated - so their
.lldbinit file will give a warning each time it is sourced, but it will
continue to work.
I think the most important thing to consider with this PR are the UI of
all the different ways settings are accessed and viewed. This PR adds a
[128 lines not shown]
[MLIR][PDL][Test] Fix memory leaks in testNullPDLValueArg (#244344)
https://github.com/llvm/llvm-project/pull/228456 added
`testNullPDLValueArg` in `mlir/test/CAPI/pdl.c`, which fails under
LeakSanitizer on the ASan buildbot.
`mlirRewritePatternSetFromPDLPatternModule` and
`mlirFreezeRewritePattern` move the contents out of their input handles
without freeing the heap-allocated containers themselves, and
`FrozenRewritePatternSet` leaves the lowered `OwningOpRef<ModuleOp>`
inside the `RewritePatternSet`. Passing the `MlirRewritePatternSet` as
an unnamed temporary and omitting the destroy calls therefore leaked
`MlirPDLPatternModule` and `MlirRewritePatternSet`.
This PR destroies both `pdlModule` and the intermediate `patternSet`
after freezing. This is the same pattern in `mlir/test/CAPI/rewrite.c`.
Assisted-by: Gemini
[lldb] Add SBInitializationOptions (#244066)
Add SBInitializationOptions and an SBDebugger::Initialize overload that
takes it, for choices a host has to make before LLDB initializes. A
setting or an SBDebugger method comes too late for those.
The class has no options yet.
Assisted-by: Claude
[libc] Add a handful of missing includes (#244361)
This PR adds a few missing includes and their CMake dependencies.
I'm looking to add Bazel rules for these headers. Bazel surfaced these
missing includes because it parses/validates each header on its own.
CSKY: Use LastSubtargetCache in getSubtargetImpl (#242778)
Migrate to the new common pattern for targets to cache the last
result.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
[Offload][AMDGPU][NFC] Introduce per-device runtime options (#239816)
This PR:
- Introduce per-device runtime options;
- Enable flexible setting for default values;
- Move AMDGPU queue and SDMA settings into the new options structure to
show the usage;
- No changes to the existing behaviors and defaults;
- Can be extended to support configurations from profiles.
RFC can be found:
https://discourse.llvm.org/t/rfc-offload-amdgpu-device-specific-runtime-defaults-for-the-openmp-amdgpu-plugin/91613
Assisted by GPT5.6
[LLVMABI] Treat data member pointers as scalars (#244140)
Match Clang, which passes atomic data member pointers directly on x86-64
Required for https://github.com/llvm/llvm-project/pull/223259
CGExprCXX: emit family and allockind attributes (#239732)
This allows us to remove the special knowledge about C++ allocation from
LLVM's MemoryBuiltins.cpp, instead trusting attributes to communicate
the important properties.
Annoyingly, clang has to grow a little bit of hard-coded knowledge about
mangled symbol names in order to actually get the most-basic-matching
::operator::new when working out the alloc-family attribute. I spent
some time trying to do this "right" by looking up the available
operators new and finding the best one, but that's super tricky and this
has the virtue of working and being pretty obviously correct when
compared to the old code.
Happily, clang now emits allocator family attributes for custom
allocators like the `__hot_cold_t` overloads in `new_hot_cold.cpp`
(which `isReplaceableGlobalAllocationFunction` in clang recognizes),
allowing us to remove that special knowledge from LLVM.
[6 lines not shown]
[clang] Don't relocate DWARF on 32-bit ARM and x86 Mach-O (#244069)
On 32-bit ARM and x86, Mach-O uses scattered relocations, which identify
their target by address. Relocatable DWARF puts every __DWARF section at
address 0, so these relocations become ambiguous: a line table's
reference to a file name in __debug_line_str resolves to the first
function in __text instead.
Don't enable relocatable DWARF for these architectures.
Assisted-by: Claude
[dsymutil][test] Use FileCheck --ignore-case in pseudo-probe.test (#243999)
Follow-up to #243925, addressing the post-merge review comment from
@perry-ca.
Use FileCheck's `--ignore-case` option instead of piping `od` output
through `tr A-F a-f`, consistent with other tests (e.g.
`llvm/test/tools/yaml2obj/XCOFF/string-table.yaml`).
[OpenMP] Fix __kmp_invoke_microtask for arm64_32 (#243956)
On arm64_32 pointers are 4 bytes. Use 4 byte loads and stores for the
p_argv entries, the stack arguments and *exit_frame_ptr.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
[InstCombine] Check the select type in the usub.sat sign mask fold (#244281)
`foldICmpUSubSatWithAndForMostSignificantBitCmp` replaces a select with
an `and` that has the type of the `usub.sat` operands. We can't do the
replacement when the select has a different type.
This PR was assisted by AI but I reviewed all the changes.
[lldb] Fix SBCommandReturnObject::SetError dropping the error (#244317)
8789c96698e0 inverted the check, so only a successful SBError was
forwarded.
Assisted-by: Claude