interfaces: clear track6-interface as a precaution #11001
If we are not in idassoc6/track6 mode some components will still
look at track6-interface so make sure to remove this at least.
interfaces.php clears the previous settings very consistently,
but that's difficult to do in MVC without adding more logic so
eventually the backend should be fixed to live with the new world
order.
[X86][AMX] Fix use iteration when reloading tiles in FastPreTileConfig (#228724)
`reload()` moved the rewritten operand off the use list being iterated,
so only the first use of a tile was reloaded. A DBG_VALUE was also
treated as a use; when it came first, the real use kept the clobbered
tile and `FastRegAlloc` crashed.
Iterate the non-debug uses with `make_early_inc_range`. Debug uses are
no longer reloaded, so `FastRegAlloc` drops their location.
Fixes #228712
Assisted-by: Claude Opus 5.5
[SelectionDAG] avoid rounding exact f32->bf16 (STRICT_)FP_ROUND
For f32-to-bf16, DAGTypeLegalizer::SoftPromoteHalfRes_FP_ROUND currently
ignores the Trunc flag and unconditionally lowers ISD::FP_ROUND to
ISD::FP_TO_BF16 as follows:
- On X86 targets with +avx512bf16 or +avxneconvert, ISD::FP_TO_BF16
lowers to vcvtneps2bf16, which is lossy (it flushes subnormals to
zero and quietens sNaNs.)
- On targets without hardware bf16 conversion instructions, it performs
rounding via a runtime libcall (e.g. __truncsfbf2) or a software
rounding sequence (which can also be lossy, e.g. quieting sNaNs).
The above is unnecessary and lossy; bitcasting to i32 and extracting
the upper 16 bits is cheaper and lossless. Do that.
Tested:
[13 lines not shown]
[CIR][AMDGPU] Add support for AMDGCN raw buffer store format builtins (#223112)
Adds codegen for the following AMDGCN raw buffer store format builtins:
- __builtin_amdgcn_raw_buffer_store_format_v4f32 (v4f32)
- __builtin_amdgcn_raw_buffer_store_format_v4f16 (v4f16)
These are lowered to the corresponding
`llvm.amdgcn.raw.ptr.buffer.store.format` intrinsic.
[CIR][AMDGPU] Add support for raw ptr buffer atomic builtins (#223137)
Adds codegen for the following AMDGCN raw pointer buffer atomic
builtins:
- __builtin_amdgcn_raw_ptr_buffer_atomic_add_i32
- __builtin_amdgcn_raw_ptr_buffer_atomic_fadd_{f32,f64,v2f16}
- __builtin_amdgcn_raw_ptr_buffer_atomic_fmin_{f32,f64}
- __builtin_amdgcn_raw_ptr_buffer_atomic_fmax_{f32,f64}
These are lowered to the corresponding
`llvm.amdgcn.raw.ptr.buffer.atomic.*` intrinsics.
Co-Authored-By: Claude Opus 5
---------
Co-authored-by: Claude Opus 5 <noreply at anthropic.com>
[mlir][tosa] Fix no op clamp canonicalization when nan_mode = ignore (#229887)
When nan_mode = ignore, a no op clamp should not be folded. This is
because if a value of NaN is specified in the input, the output becomes
the minimum specified value. A regression test with clamp bounds of
infinity is provided.
Fix force_disable_versioning object lock test
## Problem
`sharing.s3.force_disable_versioning` refuses a bucket with object lock by raising a single `ValidationError`, which the API client re-raises as that same class. The test expected `ValidationErrors`, so the refusal escaped `pytest.raises` and the test failed.
## Solution
Catch `ValidationError` and assert on its `errmsg` directly. The latch xattr is now set with `os.setxattr` through `python3` over ssh instead of `setfattr`, following the precedent in `tests/sharing_protocols/smb/test_smb_protocol_base.py`, which sets xattrs on the remote host the same way.
(cherry picked from commit 63b25f2f269514a17585987b0364f771a5fed47c)
NAS-144425 / 28.0.0-BETA.1 / Fix force_disable_versioning object lock test (#19988)
## Problem
`sharing.s3.force_disable_versioning` refuses a bucket with object lock
by raising a single `ValidationError`, which the API client re-raises as
that same class. The test expected `ValidationErrors`, so the refusal
escaped `pytest.raises` and the test failed.
## Solution
Catch `ValidationError` and assert on its `errmsg` directly. The latch
xattr is now set with `os.setxattr` through `python3` over ssh instead
of `setfattr`, following the precedent in
`tests/sharing_protocols/smb/test_smb_protocol_base.py`, which sets
xattrs on the remote host the same way.
NAS-144429 / 28.0.0-BETA.1 / Validate no_unmount against force_unmount in zfs.resource.rename (#19989)
## Problem
force_unmount defaults to True and truenas_pylibzfs refuses
force_unmount together with no_unmount, so passing no_unmount on its own
failed with a raw ValueError.
## Solution
The pair is now rejected up front with a ValidationError, so a caller
asking for no_unmount has to set force_unmount to false explicitly
rather than having one of the flags silently ignored. The force_unmount
description says so.
py-virtualenv: updated to 21.14.7
Bugfixes - 21.14.7
Escape the environment name in the bash activator for both of bash’s PS1 passes, so a name or --prompt value with a backslash before $(...) or backticks no longer runs as a command each time bash draws the prompt
[libc] Add linux syscall wrappers for exit and exit_group (#230528)
Add dedicated linux syscall wrappers for SYS_exit and SYS_exit_group,
and update existing call sites to call the appropriate one instead of
using raw syscall_impl:
- exit_group terminates all threads in the thread group (process), so it
is used by internal::exit, posix_spawn child error exits, and do_start
initialization failure paths.
- exit terminates only the calling thread, so it is used in thread_exit
and tls init error paths.
Assisted-by: Gemini
py-wcmatch: updated to 11.1
11.1
- **NEW**: Add support for Python 3.15.
- **FIX**: Fix `WindowsPath` subclass construction on Python 3.12+
- **FIX**: Fix symlink prefixes for multiple `GLOBSTAR` captures
[SelectionDAG] Preserve demanded lanes in sign-bit queries (#230093)
Forward demanded lanes through multiplication and truncation.
Assisted by: GPT 6.1 Sol
---------
Co-authored-by: Matt Arsenault <arsenm2 at gmail.com>
avoid setting BUS_DMA_64BIT on 32-bit limited hardware and sparc64
On sparc64 the IOMMU is bypassed when the BUS_DMA_64BIT flag is set.
With addresses having the high bit set, which requires support for full
64-bit addresses even if the memory is physically located below 4G.
Initial patch from Ted Bullock. Feedback and ok on an earlier diff
from kettenis@
Ted reports this avoids:
[drm] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD)
on a sparc64 machine with an XVR-100.
[Mips] Update R6 FP condition checks after kill flag removal (#231107)
The instruction-selection checks added by #226838 still expect `killed`
operand flags. #229069 removed those flags from SelectionDAG emission
before #226838 landed, causing `r6-fp-condition-subregs.ll` to fail on
the CI after land.
Remove the five stale `killed` expectations.
Assisted-by: OpenAI Codex
