[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
bhyve/riscv: fix PCIe FDT interrupt-map entry stride
In bhyve arm64, each PCIe interrupt-map entry spans 10 cells because the
ARM GIC specifies #interrupt-cells = 3. On RISC-V, the APLIC uses
#interrupt-cells = 2, so each entry spans only 9 cells.
When the PCIe FDT code was originally adapted from arm64, the property
allocation size and cell assignments were reduced to 9 cells per entry,
but the loop multiplier retained the 10-cell stride. This caused the
interrupt-map array to be packed incorrectly with gaps, breaking PCI
interrupt routing in guest operating systems and overflowing the
allocation by 16 cells.
Correct the loop stride to 9 cells so the interrupt map is properly
formed.
Reviewed by: jrtc27
Fixes: 7ab1a32cd43c ("bhyve/riscv: Initial import")
MFC after: 3 days
[25 lines not shown]
[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.
ZTS: slog_replay_volume_split_*: write with stride_dd (#19917)
slog_replay_volume_split_boundary and slog_replay_volume_split_write
fail on every ubuntu26 CI run since its kernel moved to 7.0.0-43:
the replayed data matches, but no split write was logged or merged.
The tests make one 512K or 768K O_DIRECT write(2) to the zvol with
dd, so that it reaches the zvol as one request and is logged as one
TX_WRITE record split over several log blocks. Ubuntu 26.04's dd is
uutils dd, which reads into a buffer that is not 512-byte aligned.
Kernel 7.0.0-38 let that O_DIRECT write through to the zvol as one
bio; 7.0.0-43 rejects it with EINVAL, as it already did for other
block devices with the default 511 dma_alignment. uutils dd then
clears O_DIRECT and writes again through the page cache, so the zvol
gets 128 or 192 4K bios, each logged as its own small record.
Write with stride_dd -D instead: its buffer is page-aligned, and it
fails rather than retry without O_DIRECT.
[2 lines not shown]
[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.
nix: the platform names the nixpkgs-illumos commit it was built with
The pin moves to nixpkgs-illumos 432283b and records the commit's date;
default.nix gives the pin to the build when it fetched the recipes at
it, so gitstatus.json names that commit. A checkout of nixpkgs-illumos
standing in (NIX_PATH, -I or --arg nixpkgsIllumos) is named by its own.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
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>
NAS-145323 / 27.1.0 / Only accept a report file name in audit.download_report
audit.export creates each report directly in the user's report
directory, so report_name must be a single file name. Refuse a name
that is empty, is "." or "..", or contains "/" or a NUL byte.
Open the report with safe_open, which refuses a symlink anywhere in
the path, and serve it from that file once it is confirmed to be a
regular file. This replaces the separate existence and file type
checks on the path.
(cherry picked from commit 73b9dd025a1d75ed63fd21491629804e3107af6a)
[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]
shader-slang: update to 2026.22.1
- Rank the numerics any/all mask wrappers at the fallback tier
- Organize compiler files into concern directories
- Preserve source locations on calls rebuilt by type legalization
- Check generated tests against their generators in CI
- Keep byte-address buffer loads at the call site
- Preserve scalar and composite SSA in direct SPIR-V emission
- Return positive exit codes from slangc
- Enable OptiX in NVRTC for optix_coopvec compute shaders
- Fix silent test failure when the output file is blocked
- Fix an infinite loop in preprocessor expansion of function-like
macros
- slangd: Remove redundant terminator character when formatting
- Clarify descriptor reflection indices and Vulkan offsets
- Bump go.opentelemetry.io/otel/trace from 1.44.0 to 1.47.0 in
/extras/scaler
- Do not clone debug information outside of a function when inlining
- Diagnose struct-inheriting structs as entry-point varyings
[31 lines not shown]