[MIR] Drop the numeric flag from the operand count test
An inline asm operand flag written as an immediate holds its register
class's TableGen ID, so adding a register class can change the
immediate, though the class stays the same. The "ops:N" syntax lets
tests write every flag symbolically instead. The new test's numeric flag
had no class, but it was still an immediate, and other tests already
check that a numeric flag prints with its count: peephole-copy.mir,
callbr-asm-kill.mir, and scavenge-clobbered-reg.mir.
Assisted-by: Claude Opus 5.5
[hwasan] Disable aliasing mode runtime and tests on Android (#235414)
HWASan x86_64 aliasing mode
(`-fsanitize-hwaddress-experimental-aliasing`)
is only implemented on Linux (`hwasan_dynamic_shadow.cpp` does not set
up
`MapDynamicShadowAndAliases` under `SANITIZER_ANDROID`). Skip building
the
`hwasan_aliases` runtime on Android in
`compiler-rt/lib/hwasan/CMakeLists.txt`
and exclude Android from `supported_os` in
`compiler-rt/test/hwasan/lit.cfg.py`
when aliasing mode is enabled.
Assisted-by: Gemini
[test][compiler-rt] Set HOME and TMPDIR via re-exec in sanitizer_set_report_path_test (#235534)
Setting `HOME=%device_rundir/%t.homedir` in the lit `RUN:` line leaves
the
device path in the host `os.environ` when `android_run.py` invokes
`adb`,
causing `adb` 37+ (`KnownWifiHostsFile`) to abort trying to create
`$HOME/.android` on the host.
Set `HOME` and `TMPDIR` from `argv[0]` inside `main()` and re-exec the
test
binary so `/proc/self/environ` has the updated paths on the target
without
modifying the host environment.
Assisted-by: Gemini
[ARM] Prevent debug instructions from blocking SUB/CMP folding (#234919)
A `DBG_VALUE` between an ARM subtraction and its matching compare hides
the
compare from `ARMBaseInstrInfo::shouldSink`. MachineSink can then sink
the
subtraction into a successor, preventing `optimizeCompareInstr` from
folding
the pair into `SUBS`; with debug information this leaves an extra `CMP`.
Look past debug instructions when checking the adjacent compare, while
keeping
pseudo probes as barriers. The regression test checks both the debug
input and
the same input after debug information is stripped.
This issue was found by a non-AI automated testing tool. AI assisted
with the analysis and development of the fix.
security/vuxml: adjust linux-rl9-libxslt package for b0a3466f-5efc-11f0-ae84-99047d0a6bcc (+)
Rerolled linux-rl9-libxslt-1.1.34_5 now includes fixes for mentioned CVEs
security/vuxml: adjust linux-rl9-libxslt package for b0a3466f-5efc-11f0-ae84-99047d0a6bcc (+)
Rerolled linux-rl9-libxslt-1.1.34_5 now includes fixes for mentioned CVEs
[libclc] Support fp32 subnormal inputs and outputs in SPIR-V sw fma (#233791)
`__clc_sw_fma` previously assumed all non-zero inputs were normal floats
(extracting biased exponent `0` as `-127` with the implicit leading bit
`0x800000` set) and unconditionally flushed results with exponent `<=
-127` to zero. On devices that support fp32 subnormals and use software
fma, this caused `fma`, `expm1`, and `erf` to fail the CTS.
Normalize non-zero subnormal inputs using `__clc_clz` and, when fp32
subnormals are supported (`!__clc_denormals_are_zero_fp32()`),
right-shift the significand before rounding for exponents in `[-150,
-127]` so subnormal outputs and subnormal-to-normal rounding overflows
are rounded to nearest-even.
