interfaces: generalise the dhcp6c_script using the new IFNAME variable #7647
The file was conceptually created in d36f0f4f62557 and before was a single
command line script... so add appropriate copyrights from that time onward.
Many thanks to Martin for pinoeering this back in the day!
[AArch64][llvm] Allow some `tlbip` insns to be used with only +tlbid
Allow `tlbip` instructions containing *E1IS*, *E1OS*, *E2IS* or *E2OS*
to be used with `+tlbid` or `+d128`. This is because the 2025 Armv9.7-A
MemSys specification says:
```
All TLBIP *E1IS*, TLBIP*E1OS*, TLBIP*E2IS* and TLBIP*E2OS* instructions
that are currently dependent on FEAT_D128 are updated to be dependent
on FEAT_D128 or FEAT_TLBID
```
[mlir][gpu] Add address space modifier to gpu.barrier (#177425)
This is a takeover of PR ##110527
This commit adds an optional list of memory fences to gpu.barrier,
allowing users to specify which memory scopes they wish to fence
explicitly, while leaving the default semantics (which are equivalent to
calling for a global and local fence by analogy to CUDA's __syncthreads)
unchanged. The new expanded semantics are implemented for SPIR-V and for
the AMDGPU backend.
See also
https://discourse.llvm.org/t/rfc-add-memory-scope-to-gpu-barrier/81021/2?u=fmarno,
where the default behavior of a gpu.barrier was hashed out (though note
that the examples based on VMCNT are outdated for AMDGPU in that memory
fences can now be annotated with the correct set of address spaces).
This commit also deprecates amdgpu.lds_barrier for usecases that don't
[9 lines not shown]
[LSR] Add unequal cost eval for dropping solutions
Some corner cases where a baseline solution is
equal to the strength reduced solution offer
regression cases when the evaluated solution is
allowed, we change this to allow equal solutions
to be dropped as well, keeping all the better
solutions to strength reduce.
[ConstraintElim] Strip IsKnownNonNegative (NFC) (#177993)
The IsKnownNonNegative field is redundant, as the use of ValueTracking's
isKnownNonNegative subsumes this.
Proof: https://github.com/dtcxzyw/llvm-opt-benchmark/pull/3390
[flang,openacc] Limit operations hoisting from acc.loop. (#177727)
This patch implements `OperationMoveOpInterface::canMoveOutOf()`
method for `acc.loop`, such that even Pure operations are not hoisted
by LICM if any of their operands are referenced in the data operands
of `acc.loop`. Related to #175108.
Reland "[NVPTX] Validate user-specified PTX version against SM version" (#177459)
Original commit message:
> When users explicitly specify a PTX version via -mattr=+ptxNN that's
insufficient for their target SM, we now emit a fatal error. Previously,
we silently upgraded the PTX version to the minimum required for the
target SM.
>
>When no SM or PTX version is specified, we now use PTX 3.2 (the minimum
for the default SM 3.0) instead of PTX 6.0.
---
The following commits should fix the failures that arose when I
previously tried to land this commit:
- 9fc5fd0ad689eed94f65b1d6d10f9c5642935e68 should address the
`llvm-nvptx*-nvidia-*` build failures:
[3 lines not shown]
Reapply "AMDGPU: Use real copysign in fast pow (#97152)"
This reverts commit bff619f91015a633df659d7f60f842d5c49351df.
This was reverted due to regressions caused by poor copysign
optimization, which have been fixed.
[SystemZ] Support fp16 vector ABI and basic codegen. (#171066)
- Make v8f16 a legal type so that arguments can be passed in vector
registers. Handle fp16 vectors so that they have the same ABI as other
fp vectors.
- Set the preferred vector action for fp16 vectors to "split". This will
scalarize all operations, which is not always necessary (like with
memory operations), but it avoids the superfluous operations that result
after first widening and then scalarizing a narrow vector (like v4f16).
Fixes #168992
[libc++] Measure additional metrics when running SPEC benchmarks (#177669)
This patch adds support for measuring additional metrics like
max RSS, retired instructions and more when running the SPEC
benchmarks.
Fixes #177611
comms/chirp: update to 20260123
- use nightly tarball
- LOCAL secondary as old nightlies are deleted from upstream immediately
- restore USE_PYTHON=pep517 as setuptools is assumed
- expose test suite
Event: Winter Field Day 2026
Event: Snowstorm Special January 2026
NAS-139399 / 26.0.0-BETA.1 / Handle stateful SMB directory services (#18072)
Directory services secrets will be clustered when stateful SMB failover
is enabled. This requires some logic to sync from TDB to CTDB and
impacts how we restore config.
NAS-139478 / 26.0.0-BETA.1 / Improve failover handling for services (#18103)
This commit addresses two issues:
1. Certain ctdb databases will be reinitialized if the client opening
database is the first to open. This means that we need the SMB server on
standby controller running prior to failover events and we need to not
issue a restart during failover processing.
2. We have some services that are dependent on directory services health
and recovery and so their restart is managed by directoryservices.setup
call within failover event to become vrrp_master. This commit removes
redundant earlier restart of these services.
libsys: add pdrfork_thread() on x86
Reviewed by: asomers
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D54879
