[AMDGPU] Unmark wave reduce intrinsics for constant folding
The `add`, `sub`, and `xor` wave reduction intrinsics cannot
be constant folded, as `add` and `sub` need to be multipled
by the number of active lanes, and `xor` depends on the parity
of the number of active lanes.
[ELF] Fix heap-use-after-free with INPUT(relative-path) (#193146)
`ScriptParser::addFile` Case 4 (relative path resolved against the
script's parent directory) passes a `SmallString<0>` stack local by
StringRef, causing asan error after #191690.
Fix with ctx.saver similar to other cases.
[X86] Quote symbol names that collide with registers/keywords in Intel syntax (#186570)
When outputting Intel syntax assembly, symbol names that match register
names (e.g., `rsi`, `rax`) or keywords (`byte`, `ptr`, etc.) must be
quoted, otherwise the assembler parses them as registers/keywords
instead of symbol references.
Fix this by populating MCAsmInfo::ReservedIdentifiers with all X86
register names and Intel syntax keywords. isValidUnquotedName() checks
this set and forces quoting when a symbol name matches.
```
% cat rsi.c
void rsi(void); void foo(void) { rsi(); }
// old clang
% clang -c rsi.c -save-temps -masm=intel -fno-pic -o - | llvm-objdump -dr -
...
4: ff d6 callq *%rsi
[14 lines not shown]
[clang][NFC] Prevent scope pollution from repeat type specifiers
Fixes #187664
When parsing `type-specifier {class,union,struct,enum,etc} nested-name`
ParseClassSpecifier and ParseEnumSpecifier both operated on the current
declaration scope on the assumption that they were the only type
specifier. Of course in incorrect code that assumption is false, and
as a result when parsing the name specifier they would pollute the
the real scope.
This is not relevant to the semantic correctness: the error is detected
and reported. The problem is that the subsequent state is not correct,
though not in a way that impacts functional behavior of release builds.
In assertion builds however this is detected (via a somewhat obtuse path)
when we attempt to plant namespace location information from the invalid
declaration on the initial declaration.
[3 lines not shown]
[AMDGPU] Unmark wave reduce intrinsics for constant folding
The `add`, `sub`, and `xor` wave reduction intrinsics cannot
be constant folded, as `add` and `sub` need to be multipled
by the number of active lanes, and `xor` depends on the parity
of the number of active lanes.
[AMDGPU] Unmark wave reduce intrinsics for constant folding
The `add`, `sub`, and `xor` wave reduction intrinsics cannot
be constant folded, as `add` and `sub` need to be multipled
by the number of active lanes, and `xor` depends on the parity
of the number of active lanes.
py-redis: updated to 7.4.0
7.4.0
Bug Fixes
Fix AttributeError in cluster metrics recording when connection is None or ClusterNode object instance is used to extract the connection info
Fixing security concern in repr methods for ConnectionPools - passwords might leak in plain text logs
Refactored connection count and SCH metric collection
Experimental Features
-Refactored health check logic for MultiDBClient
redis: updated to 8.6.2
Redis 8.6.1 Released Mon 23 Feb 2026 10:00:00 IST
Upgrade urgency SECURITY: There is a security fix in the release
Security fixes
- A user can manipulate data read by a connection by injecting \r\n sequences into a Redis error reply
Bug fixes
- `HOTKEYS`: The `INFO` command may display module information, and the missing `HOTKEYS HELP` subcommand has been added
- Bug in RDB loading prevented hash table expansion, increasing load time
Redis 8.6 GA (8.6.0) Released Tue 10 Feb 2026 16:00:00 IST
This is the General Availability release of Redis 8.6 in Redis Open Source.
[10 lines not shown]
