unit: check fixture setup and output cleanup results
Check the fat-ZAP upgrade operations and memory-stream closes directly,
so their failures cannot be hidden by later assertions on the contents.
Reject a failure to disable core dumps in the btree death-test child
with a nonzero exit. An assertion there would produce the same SIGABRT
that the test expects from the btree operation.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Reviewed-by: Rob Norris <rob.norris at truenas.com>
Signed-off-by: Kamil Monicz <kamil at monicz.dev>
Closes #19467
[Flang][test] Use x86 triple (#235354)
`REAL(10)` is only available on x86 targets. x86-registered-target
enabled in #235068 is insufficient, it also needs to be compiled to the
x86 target triple. Apply the same -triple as other tests such as
flang/test/Semantics/real10-x86-01.f90 do.
Note: Some constant foldings are only available if the flang compiler
itself runs under x86, but folding is not what is tested here.
Should fix the
[clang-aarch64-sve-vls-2stage](https://lab.llvm.org/buildbot/#/builders/4)
buildbot
[CIR][CUDA] Add host-side surface registration support (#225146)
Related: #179278.
This patch adds host-side registration support for CUDA built-in surface
references in CIR.
Previously, CIR recognized CUDA surface variables during registration,
but host-side surface handling was not implemented. This change
preserves the surface type information in CIR registration metadata and
emits the corresponding `__cudaRegisterSurface` runtime registration
call.
## Changes
- Internalize CUDA surface and texture host shadow variables to match
original CodeGen behavior
- Extend `CUDAVarRegistrationInfoAttr` with the CUDA surface type
- Extract the surface type from the CUDA surface template arguments
[11 lines not shown]
libspl: keep native backtraces usable under Valgrind
Native unwinding inspects register snapshots and probes process memory.
Memcheck can report these operations while handling an assertion,
obscuring the failure that triggered the backtrace.
Disable Valgrind error reporting on the calling thread while generating
the native backtrace, then restore the previous reporting state. Keep
the native registers, symbolization and caller-selected descriptor,
including stderr redirected after Valgrind starts. Detect the optional
client-request headers during userspace configuration.
This scope also hides genuine errors encountered while unwinding.
Add destination tests for redirected stderr and custom descriptors.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Signed-off-by: Kamil Monicz <kamil at monicz.dev>
Closes #19459
[VPlan] Drop poison-gen attributes & metadata on replicated clones. (#234613)
VPReplicateRecipe::execute clones the original instruction, carrying
over all metadata & attributes.
Clear poison-generating attributes & metadata, to make sure we only
apply the attributes & metadata carried by the recipe itself.
PR: https://github.com/llvm/llvm-project/pull/234613
[Flang] Reject unexpected REAL kinds when lowering literals
Kind 8 was the default arm of the real-literal switch, so any other kind
was parsed as an IEEE double. Handle kind 8 explicitly and abort on an
unsupported kind.
Hash the operand kind of a relation
Relational::kind() is the logical result kind, which is always 4, so
relations of different operand kinds hashed the same. Hash the operand
kind instead.
Grok finding another mistake by GPT/Claude
[Driver][SYCL] Link libclang_rt.builtins.bc for spirv64 at compile time via getDeviceLibs (#218528)
Add support for linking `libclang_rt.builtins.bc` for the `spirv64`
target at compile time by integrating it into the SYCL `getDeviceLibs`
mechanism. This ensures built-in runtime library functions are available
for SYCL device code targeting `SPIR-V` 64-bit.
Re-land of https://github.com/llvm/llvm-project/pull/212550 (Only Clang
Driver changes)
---------
Co-authored-by: Claude Sonnet 4.6 <noreply at anthropic.com>
