[AMDGPU] Use integer LLTs for work-item IDs (#224519)
Type work-item ID preloaded values and special entry-function live-ins
as i32, matching the intrinsic result and the existing GlobalISel and
SelectionDAG lowering. This prevents an s32 live-in type from reaching
the divergent G_AND and lets VgprToVccCopy preserve its source LLT
directly.
The original failure was a GlobalISel cannot-select abort on a 32-bit
VGPR G_AND produced from `llvm.amdgcn.workitem.id.x`. This follows up
#220987 by fixing the type at its producer instead of coercing it in
register-bank legalization.
A lot of tests need to be migrated because of this, owing to the
Extended LLTs change in https://github.com/llvm/llvm-project/pull/207419
Assisted-by: Codex
Signed-off-by: Keshav Vinayak Jha <keshavvinayakjha at gmail.com>
Co-authored-by: GPT-5 <noreply at openai.com>
mail/exim: 4.100 -> 4.100.1
Security: GCVE-25-2026-09-50-1, GCVE-25-2026-09-51-1,
GCVE-25-2026-09-55-1, GCVE-25-2026-09-56-1
Requested-by: The Doctor <doctor at doctor.nl2k.ab.ca>
Merge tag 'pci-v7.3-fixes-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci
Pull PCI fix from Bjorn Helgaas:
- Enable clock after core reset is asserted to fix enumeration
regression on i.MX6Q Apalis platforms with ASM1061/ASM1062 SATA
controllers (Richard Zhu)
* tag 'pci-v7.3-fixes-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci:
PCI: imx6: Move clock enable after core reset assertion
18413 zfs: spa_sync_upgrades() should only take lock when needed
Reviewed by: Bill Sommerfeld <sommerfeld at hamachi.org>
Reviewed by: C Fraire <cfraire at me.com>
Approved by: Gordon Ross <gordon.w.ross at gmail.com>
net/pimd: update to 3.1.0
troglobit/pimd, the upstream this port tracked, has not seen a commit since
August 2022 and its last release, 2.3.2, is from 2016. The port was pinned
to an unreleased master snapshot (2.3.2b, commit 17ae62f) because there was
nothing newer to move to.
This new fork continues the tree and releases from it. 3.1.0 brings
Anycast-RP (RFC 4610), accept-nbr-from and register-accept-from, and rescans
interfaces at runtime so a link that comes up after the daemon started becomes
a vif without a restart.
[WebKit Checkers][NFC] Extract hasPublicMethodInHierarchy from isSmartPtrCompatible (#224697)
So we can reuse it in borrow checking.
hasPublicMethodInHierarchy identifies RefCounted via 'ref' and 'deref'
public
member functions.
Borrow checking will identify CanBorrow via a 'crashIfBorrowed' public
member
function.
Assisted-by: Claude
Exclude tailcallelim test (#224708)
keeping the bot green. This failure was introduced in PR #221694, but
tailcallelimination isn't yet clean wrt profcheck
Revert "virtual_oss(8): Fix cuse.ko check"
parse_options() was moved above cuse_init(), which makes every single
regular virtual_oss invocation which uses cuse_dev_create() fail.
This reverts commit f014795ec3bd5efb88dfc249599e9665dc10a59e.
[AMDGPU][MC] Upstream gfx11/gfx12 true16 assembler test coverage
Upstream new assembler test cases, covering true16 .l/.h operands and op_sel
handling that had no upstream coverage.
[CIR][NFC] Fix compilation error CIRGenModule (#224694)
Fix deduced conflicting types for parameter when calling std::max with
unsigned long and unsigned long long, can be fixed by
`std::max(f.getAlignment().value_or(1), 2ull)` but in this line, the
alignment is always less than 2 because of the parent if condition, so
max is always 2
[AMDGPU][MC] Upstream gfx11/gfx12 true16 assembler test coverage
Upstream new assembler test cases, covering true16 .l/.h operands and op_sel
handling that had no upstream coverage.
[AMDGPU][MC] Upstream gfx12 true16 disassembler test coverage
Upstream new gfx12 disassembler test cases, covering true16 operand (.l/.h)
and op_sel decoding for f16 opcodes that had no upstream coverage:
[lldb] Follow serial outlined functions when scanning for an unwind plan (#222800)
For code-size-constrained builds the compiler's instruction outliner
finds
identical instruction sequences across functions, moves them into a
single
OUTLINED_FUNCTION_<n>, and has every user call it. Instructions from a
function's prologue, body or epilogue may all be outlined.
lldb's instruction-emulation UnwindPlan creator scans the instructions
of a
function and, following the ABI's calling convention, assumes a call
leaves the
stack and registers in a known state. That assumption does not hold for
outlined functions: when prologue and epilogue instructions are outlined
out of
the function body, the UnwindPlan misses those register spills and
restores,
which leads to inaccurate variable tracking in the caller's frames.
[20 lines not shown]
[lldb] Don't consult the plan stack for a stop an auto-continue will discard (#215522)
Fixes part (2) of #215189. The sibling PR for part (1) is #215521. The
two are
independent, but are best landed together.
When a completed thread plan auto-continues, `Thread::ShouldStop()`
still
consults subsequent plans and then discards their stop decisions. Those
calls
can change the state of the plans being consulted. In the failing case,
`ThreadPlanRunToAddress` loses the breakpoint it was running to, so the
process
runs past the requested address.
This does not require a scripted plan:
```python
# thread stopped on an enabled breakpoint site
[46 lines not shown]
[lldb] Remove the unused Process::ReadMemoryInChunks (#224656)
`Process::ReadMemoryInChunks` and its `ReadMemoryChunkCallback` typedef
have no callers left in the tree, no unit tests, and no SB API exposure.
This commit removes it.
The method was added in commit f869d6efeec8 (#129307) for the minidump
writer, which was its only caller. Then, commit 7f04a40a220e (#212641)
replaced that call with a direct loop over `ReadMemoryFromInferior` in
`MinidumpFileBuilder::ReadWriteMemoryInChunks`, leaving this method
dead.
This commit also drop the reference to this method from the description
of
`TestProcessSaveCoreMinidumpSizeMismatch.py`. The test is unchanged.
