[flang][cuda] Restrict managed data transfers to whole-array assignments (#212593)
Assignments involving managed or unified data are lowered to
`cuf.data_transfer`, a synchronous copy. The predicate only excluded
scalar left-hand sides, so array sections were transferred too, turning
a loop that assigns one section per
iteration into a sequence of blocking copies.
Key the decision on the managed operand instead: a transfer when the
managed variable or array is whole, host code when it is a section or an
element. Managed data is host-addressable, so the host assignment is
safe. Managed function results and assignments involving device memory
are unaffected.
This is the behavior specified in the CUDA Fortran Programming Guide
3.4.1:
> An assignment statement where the right hand side is a managed array
section and
[2 lines not shown]
sysutils/rpi-firmware: Update to 1.20260521
Update the Raspberry Pi firmware binaries to the latest upstream release
to provide native support for GPT partition schemes.
This update is related to the NanoBSD Reimagined GSoC 2026 project,
which aims to standardize on GPT layouts across all supported embedded
platforms.
Reviewed by: manu
Differential Revision: https://reviews.freebsd.org/D58197
GlobalISel: Don't use GISelMatchGenericTypes for floating point opcodes
AMDGPU ends up with same input pattern that check for v2s16 so the one
that is first in tablegen table always fires (it was v2f16 in this case).
Should explictly check for f16/bf16 and v2f16/vsbf16.
NAS-141996 / 26.0.0-BETA.3 / Fix broken unit tests (by anodos325) (#19439)
This commit fixes some broken unit tests for directory services.
Original PR: https://github.com/truenas/middleware/pull/19438
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
NAS-141996 / 26.0.0-RC.1 / Fix broken unit tests (by anodos325) (#19440)
This commit fixes some broken unit tests for directory services.
Original PR: https://github.com/truenas/middleware/pull/19438
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
Stop a container in any active state when tearing down tests
## Problem
The `container` fixture only force-stops the container on teardown when it is RUNNING, but delete now refuses any container that is not STOPPED. A test that leaves one suspended fails in teardown rather than cleaning up.
## Solution
Stop it whenever it is not already STOPPED.
Say what a recursive container destroy removes
## Problem
The comment above the destroy in `do_delete` explains `recursive=True` as being about the container's own snapshots. It also destroys anything cloned from those snapshots, which is a good deal more than the comment suggests.
## Solution
Say so.
Skip the legacy container repair on HA hardware
## Problem
The repair migration runs from `core.notify_postinit`, and an HA-licensed controller does not import its pools until the failover event promotes it, so every row reads back as absent and the migration records itself as done having repaired nothing. There is nothing for it to repair there in any case: the incus migration hangs off `system.ready`, which HA ignores, so it never ran on those systems.
## Solution
Bail out on HA-capable hardware. The gate is the hardware rather than the HA license so this never runs on a controller that can be paired. While here, probe for the legacy tree through `zfs.resource.query_impl` via `call2` the way the neighbouring migration does, rather than the public method by name, and drop the docstring's claim that a failure would make the migration re-run on every boot - `migration.run` clears the `run_migration` flag regardless, so it only retries at the next upgrade.
boot0cfg: Also allow a file as a trailing argument
Modify the disk check to allow arbitrary files as the trailing argument
instead of requiring a live GEOM disk provider.
This enables modifying a boot0 binary file in-place before flashing it
to a disk via gpart bootcode, or using it directly as an argument to
mkimg's partition specification, as these tools cannot directly adjust
the parameters of the boot0 boot manager.
Reviewed by: imp, jhb
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D57310
nanobsd: Restore boot0cfg functionality
The need for this step is fading, now is mostly used to allow the
selection of just the two code partitions in the boot0 boot manager,
instead of the default of allowing all four MBR slices (the other two
being cfg and data, which cannot boot).
Reviewed by: imp
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D57311
Revert "[Codegen] Replace any_of with is_contained. NFC (#212289)" (#212794)
This reverts commit 52f6c88c2c1b6f0c10b9c8fb09ec35e147c593e3 due to
errors in the C++20 builder.
It does not revert the followup from #212711.
[OpenMP] Fix ambiguous namespace lookup with delayed template parsing (#212720)
Running `check-llvm` on Windows fails while compiling LLVMFrontendTests
with the following error:
error: reference to 'detail' is ambiguous
Clang enables delayed template parsing by default when targeting the
MSVC ABI on Windows. When ConstructDecompositionT is instantiated after
a using-directive for `llvm::omp`, both `::detail` and
`llvm::omp::detail` are
visible, making `detail::find_unique` ambiguous.
Explicitly qualify find_unique with the global namespace. This fixes
check-llvm on Windows and other environments using
-fdelayed-template-parsing, without changing behavior.
security/please: Mark DEPRECATED
- Update WWW as the old URL redirects
- Update MASTER_SITES as the old URL redirects
- Upstream repo is archived so use sudo, doas, mac_do or sudo-rs
- Set EXPIRATION_DATE 2026-08-28
(cherry picked from commit 8718467cf617dae9d562ca4100f8d81c799d3ffa)
