[AArch64][SME2] Add stridedorcontiguous pseudos for multi-vector-stores (#211551)
Select strided-or-contiguous psuedos for SME2 multi-vector stores,
allowing register allocation to choose the most profitable tuple layout.
The pseudos can then be expanded to choose the appropriate contiguous or
strided instruction after allocation.
[mlir][xegpu] Handle size-1 broadcast dim in insert_strided_slice layout setup (#211725)
This PR enhance `setupInsertStridedSliceResultLayout` to treat a size-1
source dim as a broadcast dim: keep its lane_data at 1 instead of
requiring divisibility.
Add regression tests for both the layout propagation setup and the
subgroup-to-lane distribution of such an op.
Assisted-by-claude
Co-authored-by: Claude Opus 4.8 <noreply at anthropic.com>
[AMDGPU] Fix fmul/fma legacy sign-of-zero miscompile (#203567)
V_MUL_LEGACY_F32 always returns +0.0 when either operand is ±0.0 or a
denormal treated as zero, while IEEE fmul XORs operand signs. This makes
results observably different when one operand is a runtime ±0.0:
fmul.legacy(-2.0, +0.0) = +0.0 (legacy zero clause forces +0.0)
fmul (-2.0, +0.0) = -0.0 (IEEE sign XOR: - * + = -)
The previous code folded whenever one operand matched m_FiniteNonZero()
or both were known never Inf/NaN, without accounting for sign-of-zero
divergence on the other operand.
Restructure the guard:
- Always safe: both operands are known never zero (legacy zero clause
cannot fire). Uses isKnownNeverLogicalZero to correctly account for
denormals flushed to zero under the function's f32 denormal mode.
[13 lines not shown]
[CIR] Add fenv attribute to cast operation (#212899)
This adds the optional #cir.fenv attribute to the cir.cast operation and
updates the verifier to enforce the attribute being present only when
the cast involves floating-point values.
Assisted-by: Cursor / various models
[mlir][tosa][tosa-to-linalg] Use 0 weights at skippable RFFT2D locations (#212293)
The TOSA specifications indicates that when computing the imaginary
output for locations (0,0), (0,W/2), (H/2,0), (H/2, W/2),
implementations may choose to skip the computation entirely and return
0, or compute each accumulation term as `-val_real * 0.0`.
The previous legalizations used `-val_real * sin(a)` but `sin(a)` may
not return exactly 0.0 due to representation error in the input to
`sin`.
This patch updates the legalization to instead check for indices where
`sin(a)` should be replaced by `0.0` and uses a `select` op to match the
expected behaviour according to the Specification when
tosa_extra_multiplies is set to `true`.
Signed-off-by: Ian Tayler Lessa <ian.taylerlessa at arm.com>
[lldb][docs] Document the script interpreter plugin build options (#212655)
Describe LLDB_ENABLE_DYNAMIC_SCRIPTINTERPRETERS and how it interacts
with LLDB_ENABLE_PYTHON_LIMITED_API, including the platform defaults for
both and why the Python Limited API requires dynamic script interpreter
plugins everywhere but Windows.
AMDGPU/GlobalISel: Switch more FP opcodes to extended LLTs (part 2) (#212909)
Migrate G_FPOW, G_FPOWI, G_INTRINSIC_FPTRUNC_ROUND, and FP<->INT
conversions opcodes to extended float LLTs.
Also update the relevant MIR tests.
[lldb][docs] Rewrite the MCP documentation for lldb-mcp (#212821)
The docs still describe lldb-mcp as a thin stdio-to-socket bridge that
auto-launches an LLDB and exposes a single lldb_command tool. It is now
a full featured multiplexer hosting its own sessions, with four tools
and pid-qualified URIs. Also restructure the documentation around how it
is used, with an explanation of the underlying architecture towards the
end.
[Clang] Support libstdc++ workarounds when using `-E` (#210802)
We have a libstdc++ workaround in place to address a hack in libstdc++15
that is used in the definition of `std::format_kind`. GCC accepts the
hack, while Clang does not. libstdc++ was eventually updated to remove
the hack, but we still need the workaround for some versions of
libstdc++15 (see #139560 for more information).
Whether this workaround (and others that address libstdc++ hacks) is
active depends on the value of `__GLIBCXX__`. This stops working if
someone first preprocesses the input (via `-E`) and then attempts to
compile the preprocessed code with Clang (see #160314): since
preprocessing has already happened, `__GLIBCXX__` will be undefined and
the workaround will not be applied.
In case of this particular workaround, this results in `#include
<format>` failing to compile on some versions of libstdc++ if you’re
using separate preprocessing.
[17 lines not shown]
bhyve: tidy up bhyve_config.5
There are few warnings reported by mandoc -Tlint:
bhyve_config.5:255:31: WARNING: new sentence, new line
bhyve_config.5:257:43: WARNING: new sentence, new line
bhyve_config.5:422:2: WARNING: missing section argument: Xr nm_open
bhyve_config.5:469:24: WARNING: skipping no-space macro
bhyve_config.5:483:2: WARNING: wrong number of cells: 2 columns, 4 cells
bhyve_config.5:484:2: WARNING: wrong number of cells: 2 columns, 4 cells
bhyve_config.5:541:24: WARNING: skipping no-space macro
- "new sentence, new line" is a trivial formatting fix.
- "missing section": there is actually no nm_open() manual page,
so use .Nm instead of .Xr for it.
- "no-space macro": format without .Oc and .Ns, similarly to
how it is already done in bhyve.8 for VNC addresses.
- "wrong number of cells": also a trivial fix.
[4 lines not shown]
[AMDGPU] SIInsertWaitcnts: rebase async marks into the merged frame at CFG joins (#211688)
This PR fixes `WaitcntBrackets::mergeAsyncMarks` to call `mergeScore` at
CFG join block even when one of its predecessors has no AsyncMark
At a CFG join block, the upper bounds of counts from predecessors are
merged. Then,
`mergeScore` rebase each predecessor’s `Score` by the merged upper
bound. Even if a predecessor has no AsyncMark, scores of other
predecessors with AsyncMarks should be rebased by `mergeScore`.
Suppose a predecessor, bb B, without AsyncMark (Score 0) visited later
than another predecessor with AsyncMarks (positive Score), bb A. If
merging upper bounds of bb B into that of bb A increases the new global
upper bounds to UB’ from UB, bb A’s Score should be rebased by the new
UB’. Previously in that case, only UB was merged but Score of bb A was
not updated as `mergeScore` was not called due to bb B’s having zero
score.
[23 lines not shown]
[clang][docs] Update CommandLineUsage and UsersManual with some flags (#209519)
The current user-manual is missing implemented options that are useful
for machine-readable output, such as `-fdiagnostics-format=sarif` and
`-fdiagnostics-absolute-paths`.
[clang][DependencyScanning] Return failure upon CompilerInstanceWithContext failure to create target (#211607)
This was first pointed out by a static analysis scan: Success/failure
results from `CompilerInstance::createTarget` in
`CompilerInstanceWithContext::initialize` is currently being discarded.
AFAICT, `initialize` should have failed if
`CompilerInstance::createTarget` failed, as I noticed that calls in
`CompilerInstanceWithContext::computeDependencies` (which is ran right
after `initialize`) contains function calls (i.e. `CI.loadModule`) that
make references to `CompilerInstance::getTarget`: `getTarget` then tries
to obtain a reference to the very `TargetInfo` instance that the earlier
`CompilerInstance::createTarget` call failed to create.
AFAIK `createTarget` doesn't actually seem to fail currently, but I
haven't been able to find a good reason as for why success/failure from
`CompilerInstance::createTarget` should be ignored even if it failed.
But please let me know if I am not seeing something here!
IR: Use LongDoubleFormat enum for long-double-type module flag
Add parse/print helpers for the LongDoubleFormat enum, and route the
"long-double-type" module flag producers and consumers through them
instead of hardcoded strings in every location. Also clean up some
unnecessary failure checks guaranteed by the verifier.
Co-authored-by: Claude (Claude-Opus-4.8) <noreply at anthropic.com>
AMDGPU/GlobalISel: Switch some FP opcodes to extended LLTs (#212664)
Migrate G_FADD, G_FMUL, G_FMA, and G_FSUB and their strict variants,
along with G_FCANONICALIZE to use extended LLTs.
Also update the relevant MIR tests.
[VPlan] Fix optimizeFindIVReductions not negating condition of blend
Fixes #212993
#194729 made the m_Select a m_SelectLike, so FindLastSelect could now be a blend. However we were checking the first operand to see if the Cond needed inverted. A select has `select %cond, %true, %false`, a blend is `blend %false, %cond, %true`, so we were failing to negate the condition.
mail/rspamd: update to 4.1.4
pkgsrc change: remove a pkglint warning of cfgfiles.mk.
4.1.4 (2026-07-29)
Incompatible changes
* Build: rspamd now links a single shared jemalloc instance per process and
refuses a static-only jemalloc — duplicated allocators caused segfaults
at startup
Features
* WebUI: read-only users can now access the Selectors tab and the Errors
history
Bug fixes
[21 lines not shown]
net/samba4: update to 4.24.5
pkgsrc change:
* remove pkglint warnings of patches/patch-lib_util_util__crypt.c
==============================
Release Notes for Samba 4.24.5
July 28, 2026
==============================
This is a security release in order to address the following defects:
o CVE-2026-6949: TSIG packet with name compression can crash DNS
Incorrect size calculations when a TSIG record contains
compressed names can lead to a large out-of-bounds write
[72 lines not shown]
