[AMDGPU] Enable SlotIndexes compaction by default
Add TargetRegisterInfo::shouldCompactSlotIndexes() so targets can opt
in to dropping dead SlotIndexes entries before greedy allocation, one
target at a time. An explicit -greedy-compact-slot-indexes still
overrides the target. Enable it for AMDGPU, where the leftover entries
skew live range priorities enough to cause heavy spilling.
[mlir][IR] Add return value to `replaceUsesWithIf` indicating that a substitution happened (#235748)
This makes it easier/cleaner for clients to detect and propagate
`change.
For example patterns are expected to return `success` when a change
happens and thus must detect them. Returning a value avoid capturing a
flag and modifying by side-effect in the callback.
sbin/nvmecontrol: fix signedness comparison warning
sector_size is guaranteed to be non-zero here, so cast to
uint32_t to match the comparison.
This fixes the [gcc14 build in CI][0]:
/workspace/src/sbin/nvmecontrol/format.c: In function 'find_lbaf':
/workspace/src/sbin/nvmecontrol/format.c:132:60: error: comparison of integer expressions of different signedness: 'uint32_t' {aka 'unsigned int'} and 'int' [-Werror=sign-compare]
132 | if (NVMEV(NVME_NS_DATA_LBAF_LBADS, format) != lbads ||
| ^~
[0] https://ci.freebsd.org/job/FreeBSD-main-amd64-gcc14_build/5051/
Reviewed by: imp
Fixes: b991e2dd824c ("nvmecontrol: support controller-wide sector sizes")
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
[X86] Don't discard over-16 stack alignment for 32-bit interrupt handlers (#225366)
calculateMaxStackAlign assigned Align(16) instead of taking the maximum,
so an alloca with align 64 in a 32-bit handler got andl $-16 and landed
only 16-byte aligned, even though PEI had laid the frame out for 64.
With AVX512 the compiler then emits vmovaps to that object, which faults.
biology/py-crossmap: urrlib fix, move to pep517
Patch upstream issue with modern urrlib use
Patch PORTNAME issue blocking switch to pep517
Note: PORTNAME does not match PYPI upper/lower case
Leaving for now to avoid pkg-upgrade failures
PR: 299804
Reported by: patrick at crandol.com
java/openjdk17: Version 17.0.21.0.3 more cert fixes
Update to latest upstream patch version to address more issues with the
eMudhra certificate incident.
See also: https://openjdk.org/emudhra
MFH: 2026Q4
Security: CVE 2026-114820
Security: JDK-8395690
Sponsored by: The FreeBSD Foundation
(cherry picked from commit c059131000221f11bb3f1bf39eaefef8a1f3e4ef)
java/openjdk17: Version 17.0.21.0.3 more cert fixes
Update to latest upstream patch version to address more issues with the
eMudhra certificate incident.
See also: https://openjdk.org/emudhra
MFH: 2026Q4
Security: CVE 2026-114820
Security: JDK-8395690
Sponsored by: The FreeBSD Foundation
System: Routes: Configuration - finish initial version of StaticRoute->syncRoutes() which aligns installed routes with our planned set, for https://github.com/opnsense/core/issues/10569
In theory this part should bold into most of system_routing_configure(), next phase is glueing this in our existing codebase and removing the old codee.
www/py-mailman-hyperkitty: Switch to USE_PYTHON=pep517
Build with the PEP 517 frontend (setuptools legacy backend; the source
has no [build-system]); the package metadata becomes dist-info.
While here, set NO_ARCH (the port installs only pure-Python files) and
add concurrent to USE_PYTHON. Also clarify LICENSE and add LICENSE_FILE.
PR: 299862
[SPARC] Give the leaf epilogue's stack adjustment a debug location (#235247)
The stack adjustment in a leaf function's epilogue was built with an
empty DebugLoc, so it inherits the line of whatever precedes it and the
row for the return's line starts after it. A breakpoint on that line
then stops with the frame already released, and %sp-based variable
locations read the wrong slots.
Use the return's location, as the non-leaf restore already does.
The delay slot filler currently hides this by moving the adjustment
into the delay slot of the retl; it shows once that slot is not filled,
see #235235.
Assisted-by: Claude Code (Claude Opus 5.5)
Only use the user's home directory for host web shells
## Problem
Container, app and VM web shells opened by a non-root user got that user's host home directory as HOME, and the shell child started in it. Inside containers this pointed $HOME and ~ at a host path, so the image's root dotfiles were not used.
## Solution
Pass the shell type to the worker thread and use it for both the command and the environment. Host shells keep the user's home as HOME; container, app and VM shells get /root. The shell child always starts in /root, since login changes into HOME itself for host shells.
