AMDGPU: Migrate CodeGen tests to amdgpu subarch triple (14) (#209117)
Mechanically migrate the command-line target spelling on llc/opt RUN
lines in
llvm/test/CodeGen/AMDGPU from -mtriple=amdgcn ... -mcpu=<gfx> to the
folded
subarch triple form (e.g. -mtriple=amdgpu9.00-amd-amdhsa), dropping the
redundant -mcpu.
Co-Authored-By: Claude <noreply at anthropic.com> (Claude-Opus-4.8)
[AArch64][SVE] Support lowering masked loads of <4 x bf16> and <8 x bf16>
Add support for lowering masked loads of <4 x bf16> and <8 x bf16> when
target features contain "+sve".
AMDGPU: Migrate CodeGen tests to amdgpu subarch triple (13) (#208897)
Mechanically migrate the command-line target spelling on llc/opt RUN
lines in
llvm/test/CodeGen/AMDGPU from -mtriple=amdgcn ... -mcpu=<gfx> to the
folded
subarch triple form (e.g. -mtriple=amdgpu9.00-amd-amdhsa), dropping the
redundant -mcpu.
Co-Authored-By: Claude <noreply at anthropic.com> (Claude-Opus-4.8)
[lldb] Correct alignment of register fields (#209140)
In #188049 the alignment of register names for the raw value part "pc =
0x..." changed.
This resulted in many register fields being 2 spaces off where they
should be, because the stream we were printing to had a 2 space indent
set where it had none before.
This is actually a bug in the original field formatting code. It assumed
the stream had no indent level of its own. So the fix is to indent using
the stream (the 2 spaces), then indent to where the register name ends.
devel/immanent-checker: new port
Immanent Checker validates project structure and source-code expectations
through configurable check suites. It can inspect full projects, filtered
project trees, directories, and files, and can report findings in gcc-style or
JSON output.
This port installs the released PHAR executables for immanent-checker and
immanent-parser.
Sponsored by: P. Variablis
py-hatchling: update to 1.31.0.
Fixed
Only rewrite the shebang of a shared script when a Python
shebang is present on the first line, preserving binary files
and other content verbatim instead of dropping leading bytes.
devel/libbson: Fix build when DOCS=off
The DOCS option were installing both HTML documentation
and manpages but these manpages weren't covered in the
plist with the DOCS substition, so we're both fixing it
and seperating them now with the new MANPAGES option.
PR: 296718
Reported by: René Thümmler <beastie at tsukaisute.de>
Approved by: Krzysztof <ports at bsdserwis.com> (maintainer)
Approved by: osa, vvd (Mentors, implicit)
py-filelock: update to 3.29.7.
3.29.7
asyncio: detect cross-instance reentrant deadlocks before the poll loop by @HrachShah in #586
🐛 fix(soft_rw): evict non-regular write marker without reading it by @gaborbernat in #588
_util: drop the dead st_mtime=0 short-circuit in raise_on_not_writable_file by @HrachShah in #589
3.29.6
serialise singleton construction in FileLockMeta by @dxbjavid in #581
_util: drop the dead st_mtime=0 short-circuit in raise_on_not_writable_file by @HrachShah in #582
test: silence fork DeprecationWarning on 3.15 by @gaborbernat in #585
py-deepmerge: update to 2.1.0.
minor: add all to strategy init by @szepesisz in #39
fix: compare by equality, not just hash, in ExtendedSet by @gaoflow in #40
docs: functools.reduce usage by @neozenith in #37
rpki-client: simplify absence of SIA handling for BRK and RSC
While RFC 6487, 4.8.8.2 clearly mandates the presence of the SIA extension
for all EE certificates, there are two exceptions. BGPsec router keys are
known to be special for no good rason, and they uphold this tradition and
the EE cert of RSCs doesn't have a SIA since that makes sense for things
that aren't distributed via the RPKI repository system.
The logic allowing these special snowflakes is currently quite contorted.
Simplify the comment to omit unnecesary fluff and implement the logic to
match the comment precisely, also suppressing a duplicated warnx(). This
does not really change anything but is much easier to follow.
ok claudio
Replace zectl with the truenas_bootenv engine
zectl is being retired in favor of the truenas_bootenv package that
ships with truenas_pylibzfs (companion commit there). The
boot_environment plugin now calls the engine in-process on
middleware's thread-local libzfs handle: query, clone, activate,
destroy and keep all go through it, utils.py with run_zectl_cmd is
deleted, and the boot-time promotion of installer-cloned datasets
uses the engine instead of parsing zfs list -j output.
Mutations serialize on an asyncio lock. A truenas:grub_pending
marker on the boot pool tracks pending menu regenerations and
setup() reconciles it on start. If the menu cannot be written,
activate rolls bootfs back. The boot pool is synced after every
menu write so the change is crash safe.
Re-activating the already-activated boot environment is allowed
again as the retry path after a failed menu regeneration, and
can_activate treats a missing truenas:kernel_version as not
activatable instead of only the literal "-".
