NAS-139183 / 26.04 / Make sure to reset ix-apps mountpoint after it is umounted (#17959)
This PR adds changes to prevent ix-apps mountpoint conflicts during
replication and setting/unsetting docker pool between manually
replicated ix-apps based pools. How we do that is:
- Inherit mountpoint property when ix-apps dataset is unmounted
(resetting from /.ix-apps)
- Exclude mountpoint property during docker.backup_to_pool and migration
replication
- Update integration tests to verify ix-apps mountpoint is correctly
inherited after pool unset, migration, and backup
ix-apps dataset does not get mounted automatically as `canmount` is set
appropriately.
[LoongArch] Disable strict node mutation to fix strict FP lowering crash (#175484)
The patch disables strict node mutation for LoongArch by setting
IsStrictFPEnabled to true.
This change fixes the current strict FP lowering crash only.
ISD::STRICT_FSETCC and ISD::STRICT_FSETCCS can be further improved.
Fixes #174606
[clang-repl] Rework layering of incremental executors. (#175448)
The original Interpreter implementation had a hard dependency on ORC and
grew organically with the addition of out-of-process JIT support. This
tightly coupled the Interpreter to a specific execution engine and
leaked ORC-specific assumptions (runtime layout, symbol lookup,
exception model) into higher layers.
The WebAssembly integration demonstrated that incremental execution can
be implemented without ORC, exposing the need for a cleaner abstraction
boundary.
This change introduces an IncrementalExecutor interface and moves
ORC-based execution behind a concrete implementation. The Interpreter
now depends only on the abstract executor, improving layering and
encapsulation.
In addition, the Interpreter can be configured with user-provided
incremental executor implementations, enabling ORC-independent
execution, easier testing, and future extensions without modifying the
core Interpreter.
radvd: use configtest debug level
In practice this doesn't really matter. I don't see any debug
messages in my installation. Normal logging should go through
and this is also very sparse.
[WebAssembly] vi8 mul cost modelling. (#175177)
We've already optimised these, so update the cost model to reflect it.
And skip the isBeforeLegalize check when lowering i8 muls, because it
then misses the cases where, say v32i8, has been type legalised into 2x
v16i8.
Also explicitly disable memory interleaving for any factor other than
two or four.
[SPIR-V] Fix Linkage capability with pushconstant (#175192)
When the SPIR-V backend handles a push constant, a new global with a
target-specific is generated. This global should have the same
visibility as the source, but turns out it was not the case: linkage was
still external, but visibility went from hidden to visible.
This causes the later passes to generate a Linkage decoration, adding
the Linkage capability, which is not compatible with Vulkan. Fixing
this.
