[mlir][SPIR-V] Add SPIRVToLLVM conversion for CompositeConstruct (#244369)
Lower structs and arrays to llvm.insertvalue chains and vectors to
llvm.insertelement chains, splitting vector constituents into elements
[mlir][SPIR-V] Fix deserializer crash on spec composite constituents (#244375)
Accept nested OpSpecConstantComposite constituents and diagnose the ones
that have no symbol to reference
Server Preview: publish the ISOs as plain .iso; keep the Pi image zipped (#682)
* Release description and README: builds are started by hand, not on every push
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
* Server Preview: publish the ISOs as plain .iso; keep the Pi image zipped
The live ISO's root is already compressed, so zipping saved ~13% (arm64:
233 MB raw, 203 MB zipped) and made users unzip before booting or
writing it. The release step unzips the ISOs; the build, its artifacts
and the boot tests are unchanged. The Raspberry Pi image stays .img.zip:
raw it's 2.4 GB of mostly empty filesystem, over GitHub's 2 GB per-file
limit, against ~190 MB zipped, and the usual Pi writers take .img.zip
directly. The README's quick start loses its unzip step.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
Server Preview: publish the ISOs as plain .iso; keep the Pi image zipped
The live ISO's root is already compressed, so zipping saved ~13% (arm64:
233 MB raw, 203 MB zipped) and made users unzip before booting or
writing it. The release step unzips the ISOs; the build, its artifacts
and the boot tests are unchanged. The Raspberry Pi image stays .img.zip:
raw it's 2.4 GB of mostly empty filesystem, over GitHub's 2 GB per-file
limit, against ~190 MB zipped, and the usual Pi writers take .img.zip
directly. The README's quick start loses its unzip step.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
Publish the Server Preview to continuous-server: ISOs, the Pi image, SHA256SUMS (#679)
The rolling release becomes continuous-server and holds only what people
install: the amd64 and arm64 live ISOs and the Raspberry Pi 5 image,
named NextBSD-Server-<arch|rpi5>-<version>, with one SHA256SUMS. The
amd64/arm64 .img stay workflow artifacts for the boot test; a tests-only
run boots the last successful build's artifact instead of a release
asset. The README's quick start boots the live ISO in QEMU.
The old continuous release is left in place; it's deleted once
continuous-server has published.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
make poll() timeout configurable, and key repeat times depend on it
for now the key repeat timers simply could event loop cycles, which can vary,
especially on slower hardware. Will need something better here.
[SelectionDAG] Use the compare operand's boolean contents when inverting a SETCC (#244992)
When LegalizeDAG expands a SETCC by inverting its condition code, it
wraps the new SETCC in getLogicalNOT() using the result type. That
picks the true value from the integer boolean contents, but the SETCC
result follows the boolean contents of the compared operand type.
On MIPS R6 FP compares produce 0/-1 while integer booleans are 0/1.
Since #173541 SETUNE, SETONE, SETO and SETNE are expanded this way, so
the inverted mask was XORed with 1, giving 1/-2 instead of -1/0, and
later combines produced wrong values.
Build the NOT with getBoolConstant() using the operand type, as the
SELECT_CC fallback below already does. Also let extractBooleanFlip()
recognize such a NOT of a SETCC, so select (not setcc) keeps folding
to a select with swapped operands.
MIPS R6 is the only target where the integer and FP boolean contents
differ, so other targets are not affected.
[3 lines not shown]
[ubsan] Initialize flags before installing deadly signal handlers (#244984)
When `SANITIZER_CAN_USE_PREINIT_ARRAY` is 0 or UBSan is linked as a
shared library, a `.preinit_array` function or DSO constructor calling
`sigaction()` can run `InitializeDeadlySignals()` before flags are
parsed, permanently skipping signal handlers requested via options.
Assisted-by: Gemini
[GVN] Merge metadata from values to load
A select from load con contain different metadata premise. Such
metadata might be incompatible and therefore be poisoned. Merge the
metadata and propogate to the previous load to eliminate this.
Asissted-by: Cluade # Test
Publish the Server Preview to continuous-server: ISOs, the Pi image, SHA256SUMS
The rolling release becomes continuous-server and holds only what people
install: the amd64 and arm64 live ISOs and the Raspberry Pi 5 image,
named NextBSD-Server-<arch|rpi5>-<version>, with one SHA256SUMS. The
amd64/arm64 .img stay workflow artifacts for the boot test; a tests-only
run boots the last successful build's artifact instead of a release
asset. The README's quick start boots the live ISO in QEMU.
The old continuous release is left in place; it's deleted once
continuous-server has published.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
Implement a locking protocol for the 68k pmap structures. This essentially
replaces the old PMAP_CRIT_{ENTER,EXIT}() markers with PMAP_{LOCK,UNLOCK}()
calls.
On systems that aren't built for MP or for pmap lock debugging, this is
all a no-op as before.
[X86][AVX10.2] Use INTR_TYPE_1OP_MASK_SAE for 512-bit VCVTTP.*QS intrinsics (#244127)
They are SAE instructions like VCVTTP.*Q.
Assisted-by: Claude Opus 5.5
Attributor: Don't report a change when no functions are internalized
internalizeFunctions returned true for an empty set, so this reported
a change for every module and invalidated all function analyses even
when it did nothing.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>