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>
[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>
OpenMPOpt: Invalidate function analyses individually
Avoid discarding analyses that never need to be invalidated, such as
TargetLibraryInfo.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
Attributor: Decide which instructions access memory in the opcode switch (#241115)
initializeInformationCache already switches over the opcode of every
instruction, and then called mayReadOrWriteMemory out of line for each
one. Decide in the switch instead, where only calls need to check their
memory effects.
Instruction counts (callgrind) with other pending attributor-light
changes applied: attributor-light sqlite3 -0.79%, kimwitu++ k -0.32%,
SPASS cnf -0.31%, consumer-typeset z08 -8.59%; the full attributor
-0.02% to -0.08%.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
ExpandVariadics: Report a change when rewriting a function without calls
This only reported a change if it rewrote a call, but it always
rewrites the function itself. In lowering mode a variadic function
without callers was changed without being reported.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
sysutils/rubygem-openbolt9: New port
OpenBolt 9.0.0 follows 5.6.0 and is the first release of the OpenBolt 9
series. The version number moves from 5 to 9 so that OpenBolt and
OpenVox share a major version. There are no OpenBolt 6, 7, or 8
releases.
Release notes:
https://github.com/OpenVoxProject/openbolt/releases/tag/9.0.0
With hat: puppet
textproc/rubygem-openvox-strings: Remove explicit dependency on openvox
OpenVox is not required by this gem, and this gem can be used by openvox
8 or 9 so remove it.
With hat: puppet