radvd: ditch the use of legacy_interface_stats() to probe for MTU
This should increase performance quite a bit. We already have the full
ifconfig data cached above. Iteration of 24e028dc10.
[flang][NFC] Use generated accessors for FIR switch operand counts (#242206)
76f452e9ad41 (#234126) declared target_operand_offsets in ODS. Remove
the hand-written attribute name helper and use the generated accessors.
This also avoids a dictionary lookup when slicing mutable successor
operands.
Assisted-by: AI
[AArch64] Mark fixed-width gathers/scatters as legal when SVE is available (#242239)
Now that we can lower all fixed-width gathers and scatters correctly
when SVE is available and the costs look sensible, I can now mark them
as legal. This does two things:
1. It stops the intrinsics being scalarised by the
ScalarizeMemIntrinsics pass just before lowering.
2. It teaches the loop vectoriser that it can now start using and
costing these intrinsics.
There are some rather odd changes to some of the loop vectoriser tests
(e.g. header_mask_and_invariant_compare in conditional-branches-cost.ll)
that are not directly related to legalising gathers and scatters. It
seems that previously we were using precomputed legacy costs for some
replicated stores, and afterwards we now use the vplan costs instead.
Unfortunately, there is a huge disagreement between the legacy and vplan
cost model for these stores which leads to a different choice of VF.
However, the end result doesn't seem unreasonable so I'm happy to look
into fixing these disparities later.
sysutils/monit: Update 6.0.0 => 6.1.0
This update introduces incompatible changes, please see the
changelog for more details. Plus many minor improvements and fixes.
Changelog:
https://mmonit.com/monit/changes/#6.1.0
This port now installs a bash completion file.
PR: 300895
MFH: 2026Q4
(cherry picked from commit d01504eb63ef33a76a3083723913674c965203e4)
sysutils/monit: Update 6.0.0 => 6.1.0
This update introduces incompatible changes, please see the
changelog for more details. Plus many minor improvements and fixes.
Changelog:
https://mmonit.com/monit/changes/#6.1.0
This port now installs a bash completion file.
PR: 300895
MFH: 2026Q4
NAS-145180 / 28.0.0-BETA.1 / Forbid creating two cloud backups pushing to the same destination (by themylogin) (#20263)
Original PR: https://github.com/truenas/middleware/pull/20254
Co-authored-by: themylogin <themylogin at gmail.com>
opnsense/miniupnpd: match the external port when deleting a NAT rule
With 0f668f1, delete_nat_rule() finds and removes the NAT rule of an
IPv4 UDP mapping, but it matches on internal address, port and
protocol only. When a client holds two UDP mappings from the same
internal port (two NAT-PMP/PCP requests, or a mapping whose
external port changed) and the later one is deleted or expires, the
earlier mapping's NAT rule is removed and the deleted mapping's
stays: the remaining mapping's outbound packets lose their external
port until it is removed too. ef2048e0 also matches the external port.
pfsync: don't apply a stale dst peer from a state update
pfsync_upd_tcp() checks each peer of an incoming update separately. A
peer whose window is behind the local copy is skipped and counted as
stale, otherwise it is copied into the state. pfsync_in_upd() and
pfsync_in_upd_c() then copied the dst peer again whenever fewer than two
peers were stale. When only the dst peer was stale, that second copy
moved the local dst window backwards.
This is the common case for a bulk transfer, where the receiver's
window barely moves and the sender's advances quickly. Once dst.seqlo
regresses by more than MAXACKWINDOW, pf_tcp_track_full() drops every
packet of the connection as PFRES_BADSTATE. Dropped packets never
update the state, so the connection stays wedged until the application
times out. The only trace is the state-mismatch counter.
Remove the extra copy. Both branches that compute sync already copy dst
when it is acceptable. Allocate dst scrub memory before the peers are
compared, so an accepted update still finds it.
[9 lines not shown]
md: Read the preloaded image length as size_t
hint.md.N.len was read as an int, so on 64-bit platforms ram disks of
4 GiB or more were truncated, or skipped at exact multiples of 4 GiB.
Reported by: llm-postcr
Reviewed by: imp
Approved by: imp
Fixes: 15925062e1ba ("biosboot: Detect memory disks from PXE")
Sponsored by: Netflix
Differential Revision: https://ron-dev.freebsd.org/FreeBSD/src/pulls/104
[AArch64][GlobalISel] Assign tail call args once in lowerTailCall (#244130)
For a non-sibcall tail call (tailcc, swifttailcc, or -tailcallopt),
lowerTailCall called determineAssignments on OutArgs to size the
outgoing stack area, and then determineAndHandleAssignments on the same
OutArgs to marshal them.
For multi-part arguments such as i128, determineAssignments rebuilds
Args[i].Flags from Flags[0] in place and sets Split on the new Flags[0].
Running it a second time therefore seeded every part with Split, so the
CCIfSplit rules misplaced the high half (skipping odd registers on
AAPCS, or using the wrong register or stack slot on Darwin) and shifted
the following arguments.
Run determineAssignments once, size the stack from that result, and
marshal with handleAssignments. This also makes the stack sizing use the
call's vararg flag instead of always assuming a non-vararg call.
rdar://193150811
[AMDGPU] Preserve noclobber after acquire operations from a different addrspace
Follow-up to #219991 to address reviewer comments:
AMDGPUAnnotateUniformValues should annotate uniform global loads as
`!amdgpu.noclobber` if the memory they are reading is never clobbered (since
kernel launch) before the load is executed.
PR #219991 strengthened the logic to consider acquire operations before the
load as clobbering (because they cause stores from other threads to be observed
by the load without a data race).
This PR weakens this criterion to ignore acquire operations that don't affect
the global address space (because they don't affect what the load in question
may or may not see). This addresses the performance-relevant case of s_barriers
with LDS-only fences.
The logic is still overly pessimistic for one-as load acquires, they could also
be ignored when looking for clobbering operations.
Disclaimer: Claude gave review comments and suggestions that I addressed during
[5 lines not shown]
www/caddy: Assume :443 Alt-Svc header for QUIC behind DNAT (#5941)
* www/caddy: Assume NAT is used when global HTTPS listener port has been changed, so advertise the Alt-Svc header on :443 instead of the changed global port
Put the toSIAtomicAddrSpace logic into a table and make it consistent with isExtendedGlobalAddrSpace
With that, the change is no longer NFC, since constant addrspaces and
addrspaces above `MAX_AMDGPU_ADDRESS` now map to `SIAtomicAddrSpace::GLOBAL`
instead of `OTHER`. This means that atomics on these addrspaces are no longer
rejected by SIMemoryLegalizer.
The tests only show differences in the generated ISA for volatile loads from
the constant addrspaces; so far we haven't waited directly after each such
volatile load, with this change we do. Arguably, these waits are unnecessary
since the accessed memory is not supposed to change, but, on the other hand,
one could argue that volatile accesses to memory that doesn't change are
pointless in the first place.
[AMDGPU][NFC] Extract SIAtomicAddrSpace and fence MMRA parsing from SIMemoryLegalizer
Determining which memory accesses are ordered by a fence is already
useful in the middle-end; this PR extracts the code to do that from
SIMemoryLegalizer, so that it can be used in middle-end transformations.
So far, unexpected suffix values for the `amdgpu-synchronize-as` were
reported when they were encountered in SIMemoryLegalizer. This PR keeps
that and doesn't report them in the middle end, since that would lead to
a lot of repeated diagnostics for them.
Disclaimer: Claude gave review comments and suggestions that I addressed
during development.
Preparation for ROCM-29879.
Assisted-by: AI
configd: restrict service stop and similar actions to wheel,wwwonly (#11233)
Addition to https://github.com/opnsense/core/commit/676d307294fe22d84b73f9639559702872b554bf
which restricted each service's own stop, the state kill actions,
clearing logs and disconnecting IPsec sessions. Still open:
- service stop
- filter flush states, filter flush sources
- system flush config_history
- ids drop alertlog
- openvpn kill
- captiveportal disconnect
None has a description, so none can be scheduled, and their only
callers in core are the web GUI and the API.
[AMDGPU] Make amdgpu.noclobber respect acquire operations (#219991)
AMDGPUAnnotateUniformValues should annotate uniform global loads as
`!amdgpu.noclobber` if the memory they are reading is never clobbered (since
kernel launch) before the load is executed. That allows the backend to use
scalar `s_load_*` instructions instead of vector loads (which would otherwise
be illegal because the scalar cache is not kept coherent with the vector
cache).
So far, loads were annotated if the thread executing the load has not clobbered
the relevant memory location, but changes from concurrent threads that were
acquired via synchronization were ignored (which is unsound).
This patch defines a semantics for `!amdgpu.noclobber` metadata in the
AMDGPUUsage and changes AMDGPUAnnotateUniformValues to respect that semantics.
Now, loads are no longer annotated if they are atomic or if an acquire fence or
load can be executed before them (since they can read from stores in other
threads in these cases).
[12 lines not shown]
[Clang][ABI][X86] Rename -msmall-int-abi-compat=clang (#243881)
To `-msmall-int-abi-compat=clang-23`, based on feedback in #236450. This
is to make it clearer that this refers to the ABI used by an older Clang
version.