net/redpanda-connect: Build with Go 1.26 on quarterly
The 2026Q3 branch still defaults to Go 1.25, while upstream's go.mod
requires go >= 1.26.6, so the build fails with GOTOOLCHAIN=local.
This is a direct commit to the branch: main already defaults to Go 1.26
and builds the port with plain USES=go:modules.
[AArch64] Cache repeated subtarget queries (NFC) (#222637)
The existing SubtargetMap caches subtargets using a key built from a subset of
relevant function attributes. Add a single-entry cache keyed by the full
function attribute set to avoid rebuilding that key for repeated queries. This
covers both repeated queries for the same function and queries for different
functions with identical attributes.
Improves CTMark geomean -0.10% on aarch64-O3 and -0.17 on aarch64-O0-g.
https://llvm-compile-time-tracker.com/compare.php?from=87d9c3c24ff5941ac08799850a6549b561c98a81&to=544bb3d9ac28bc1a28248f6b03bcd95fa85b20e0&stat=instructions:u
Assisted-by: codex
[LLVM][CodeGen][SME] Make FMA decision independent of streaming mode. (#222598)
The relevant bfloat instructions are available in streaming mode and
thus we can benefit from the same BFMLAL based lowering.
NAS-143137 / 27.0.0-BETA.1 / Drop `extra = "allow"` from interfaces schema (#19621)
This model had three undocumented fields (stp, xmit_hash_policy,
lacpdu_rate). After documenting them, the option is not necessary
anymore.
NAS-143134 / 27.0.0-BETA.1 / Do not `pop` extra fields when adapting a model if new model has `extra="allow"` (#19620)
`InterfaceEntry` in 26 has `extra="allow"`, but doesn't have
`failover_critical` defined explicitly. `failover_critical` was defined
explicitly in 27, and now it is stripped when converting to 26 API
response. We should not strip fields if target model has
`extra="allow"`, since any extra field will pass the validation
successfuly.
This PR fixed the incorrect conversion algorithm, the actual API fix
will be a separate PR.
[libc] Implement pthread_kill (#222625)
The implementation delegates to Thread::kill, which uses tgkill to
target the thread ID.
The main complication is handling zombie threads. POSIX.1-2024 requires
that pthread_kill on a terminated (zombie) thread does not return ESRCH
because the pthread_t handle is still valid. The Linux kernel reaps
threads immediately on exit, so calling tgkill on an exited thread would
return ESRCH (or worse, target a recycled TID). To handle this:
- we check the thread's detach_state first. If it's already EXITING, we
simply return success without calling tgkill (a zombie thread cannot
handle signals anyway).
- if the thread exits concurrently and tgkill returns -ESRCH, we assume
it transitioned to a zombie and treat it as success.
I've also added a tgkill syscall wrapper and replaced one raw usage of
SYS_tgkill.
[2 lines not shown]
Share the SED entitlement check between its callers
This commit makes some changes where the SED entitlement check was written out by hand in a few places instead of going through one helper. `validate_sed_license` moves out of the pool utilities, since nothing about it is pool specific, and takes the key to report under as a single string so a settings field validator can pass a bare field name while the pool paths keep passing a full schema path.
The global SED password is now checked by a field validator like everything else in advanced settings, rather than inline ahead of them, so a denial no longer pre-empts the other errors in the same payload. That needed the password merged into the dicts the settings helper diffs, because it is not a field on the entry, and it lets the helper go back to its original signature.
