AArch64: Fix optimizeCondBranch crash on an undef register (#216593)
Found by AI while working on something else.
Co-authored-by: Claude (Opus 4.8) <noreply at anthropic.com>
[lldb] Gate debugserver tests on advertised qSupported features (#214768)
Tests that need a recent `debugserver` skipped themselves with
`@skipIfOutOfTreeDebugserver`, which asks whether the stub was built in
the tree
rather than whether it supports the feature under test. A system
`debugserver`
that already ships the feature was skipped anyway, and a stale in-tree
build was
not. Every year, we remove some `@skipIfOutOfTreeDebugserver` because
the new feature shipped in system `debugserver`.
Ask the stub instead. Tests get the supported features of stub, and
only run the test if stub advertises the very feature.
`TestConsecutiveWatchpoints` keeps the decorator, because it covers a
`debugserver`
bug fix that no capability describes and it also runs against
`lldb-server`.
[27 lines not shown]
ifnet: Restore previous size of if_afdata
Struct ifnet contains an array if_afdata of AF_MAX pointers to address
information for each possible address family. Since 2013, when AF_MAX
was inadvertently changed to be equal to the highest possible value,
instead of one more than the highest possible value, this array has been
too small in theory, but this never mattered in practice because the
higher address families were not assignable to interfaces.
My recent commit which corrected the value of AF_MAX had the side effect
of breaking the KBI by changing the size and layout of struct ifnet.
This manifested itself as kernel panics when using third-party network
drivers and went unnoticed in main because if_afdata no longer exists
there. Address the issue for stable/15 and stable/14 by keeping the
correct value of AF_MAX but deliberately making if_afdata off by one,
restoring its previous size.
Fixes: ddd850aa7720 ("sys/socket.h: Fix AF_MAX")
Sponsored by: Klara, Inc.
[3 lines not shown]
libifconfig: Fix table size
Tables that have one element per protocol or address family were
previously sized by AF_MAX + 1 since AF_MAX was off by one. Now that
AF_MAX has been corrected, we need to apply the opposite correction to
these tables.
Fixes: ddd850aa7720 ("sys/socket.h: Fix AF_MAX")
MFC after: 3 days
Sponsored by: Klara, Inc.
Sponsored by: NetApp, Inc.
Reviewed by: kevans
Differential Revision: https://reviews.freebsd.org/D58827
(cherry picked from commit 79a6ad63e6afdfa00d0e625996bddf91e9f217c3)
routing: Fix table sizes
Tables that have one element per protocol or address family were
previously sized by AF_MAX + 1 since AF_MAX was off by one. Now that
AF_MAX has been corrected, we need to apply the opposite correction to
these tables.
Fixes: ddd850aa7720 ("sys/socket.h: Fix AF_MAX")
MFC after: 3 days
Sponsored by: Klara, Inc.
Sponsored by: NetApp, Inc.
Reviewed by: pouria, kevans, glebius
Differential Revision: https://reviews.freebsd.org/D58826
(cherry picked from commit 6c41d928bcd763ec60d55bec2886c05b03cf9e6a)
sys/socket.h: Fix AF_MAX
AF_MAX was always intended to be one more than the greatest allocated
value. Jeff broke this in 2013. Unfortunately, a bunch of people then
decided to adapt to the mistake instead of correcting it.
Fixes: 863c7e45628d (" - Reserve a special AF for SDP. The one we were incorrectly using before was taken by another AF.")
MFC after: 3 days
Sponsored by: Klara, Inc.
Sponsored by: NetApp, Inc.
Reviewed by: kevans, glebius
Differential Revision: https://reviews.freebsd.org/D58597
(cherry picked from commit ddd850aa7720f77b6605599655df898b16ed74cc)
[libomp] Fix hang when a fatal error is raised before library registration (#215988)
Uncovered by debug-build testing, not triggered for non-debug builds due
to absence of KMP_DEBUG_ASSERT.
Claude assisted with this patch.
sysutils/lla: update to 0.5.12
[0.5.12] - 2026-08-15
Added
Plugin Platform v2 with manifest-based packages, API-range negotiation, plugin-owned response buffers, batch decoration, typed machine-output fields, declared permissions, ordered user/system discovery, package diagnostics, and per-package checksums.
Plugin lifecycle destruction, panic isolation, bounded responses, functional contract probes, and CI/release conformance gates for every bundled plugin.
lla plugin doctor, lla plugin info <name>, and lla plugin permissions <name> for inspecting v2 installations.
security_audit plugin for unsafe permissions, SUID/SGID bits, suspicious symlinks, and exposed secret-like files.
media_inspector plugin for MIME detection, built-in image dimensions, optional EXIF, and ffprobe-backed audio/video metadata.
project_context plugin for Rust, Node, Python, and Go detection with lockfile, artifact, toolchain, and Git health fields.
trash plugin for cross-platform recoverable deletion, listing, conflict-safe restoration, and age-gated permanent emptying.
preview plugin with bat text/Markdown highlighting, chafa image rendering, safe archive listings, and built-in fallbacks.
Changed
All bundled plugins now ship with v2 manifests and are packaged as self-contained directories while legacy flat v1 libraries remain loadable during migration.
Invalid plugins are quarantined for recovery by lla clean instead of being permanently deleted.
file_remover remove now moves selected entries to recoverable trash; irreversible deletion is available only through the explicit purge action and confirmation.
[40 lines not shown]
editors/redox: update to 0.8.1
This is the last tiny set of fixes before a thorough editor rewrite, which will mostly be to clean up the scope of the project and the implementation details of some features.
Tweaked the yellow shades in the base colour scheme
Removed the perf corners widget because it's fundamentally not useful for assessing editor performance, which I somehow only just realized :)
devel/sem: update to 0.22.1
[0.22.1] - 2026-08-16
Added
sem find / sem callers / sem refs: new query verbs that answer directly from the mmap index.sem — entity definitions, direct callers (reverse edges), and direct refs (forward edges) — without touching cache.db.
sem grep <pattern>: trigram-accelerated text search over the mmap index. A required-trigram query against the index's TRIGRAM section narrows the candidate file set, each candidate is then verified with the real regex matcher against its current bytes (never stale stored content), and output is rg-compatible file:line:text. Beats rg 11-26x on giant repos (measured on the TypeScript monster and home-assistant-core corpora: 25-53ms vs. rg's 283-980ms for the same pattern). Falls back to a full scan for patterns no trigram query can be derived from.
sem review listen <diff-id-or-url> [--dry-run]: one-command agent attach to a hosted sem-cloud review. Resolves credentials, validates the diff exists, locates the review-listener plugin, and execs claude with the documented flags/env. --dry-run prints the assembled command with secrets masked, without launching or requiring claude to be installed.
Three new sem-cloud MCP tools (join_review, wait_for_branch, reply_to_branch) let an agent join a hosted code review as a live listener: long-poll for reviewer questions anchored to lines of a diff, investigate them in the repo, and stream answers back. Ships with a Claude Code plugin (integrations/claude-review-listener/) that wires the tools up and adds a read-only Stop-hook backstop for headless sessions.
sem diff's hosted upload no longer blocks on the local caller/callee relations pass. With cloud consent on, the diff snapshot uploads immediately with empty relations; the server queues enrichment and replies "enrichmentQueued" (or, against an older server, the CLI runs the existing local pass and PUTs the result afterward). SEM_RELATIONS_LOCAL=1 restores the old blocking single-upload behavior; the local relations pass's own budget is now adaptive to repo size.
Performance
Cold graph builds are 11-30% faster and peak RSS is down 17-40% on giant corpora, versus 0.21. Measured end-to-end on the shipped release binary: home-assistant-core 5.9s, TypeScript monster 11.2s, dotnet-runtime 46.7s, llvm-project 34.7s, linux 35.2s cold full-CLI (warm rebuilds: 0.2-1.3s). Every corpus improved on both the engine-only and full-CLI metrics; full methodology and per-corpus numbers are in RESOLUTION-PROFILE.md's FINALE section.
C#/C++ builds now skip re-parsing files whose facts are already known, closing the last gap in precomputed-facts reuse (JS/TS/Python/Go/Java/Rust already had it). A per-file gate proves a corpus-wide invariant — no entity's parent lives in a different file — before trusting precomputed facts wholesale, so this needed no facts-schema change. Measured on dotnet-runtime: reparse time drops from 10.6s to 65ms.
Parsed file facts now persist to disk as a content-addressed corpus, so a build that has seen a file's exact content before warm-starts it instead of re-parsing from scratch, even in a fresh process. Fixed a regression where checking a shared corpus against a large number of prior contributors got slower as the corpus grew (one repo's known-content rebuild was measured 332% slower against a 7.9GB shared corpus than a 556MB one); it now costs the same regardless of corpus size.
sem context regained a fast tier it had lost, by reading each entity's body from its own file at an indexed byte span instead of walking and hydrating the whole corpus. A prior cascade of cache removals deleted the old fast path along with a correctness bug it had, but left sem context always doing a full corpus load — measured on the TypeScript monster 1.11s down to 48ms, on a mid-size repo 0.16-0.28s down to 4.6ms. Verified byte-identical against the always-correct full-load path across both entity- and file-scoped lookups; still declines (never approximates) on a stale cache, an ambiguous name, or any entity missing a span.
Changed
[7 lines not shown]
devel/gitpane: update to 0.11.0
[0.11.0] - 2026-08-15
Added
gitpane now sleeps when nobody is looking at it. Under tmux, a lightweight probe (one tmux display-message every 3 seconds) tracks whether the pane is visible and whether the session has seen input recently, and drives three states: awake (visible and recently touched: full polling), doze (visible but input-idle for watch.doze_after_secs, default 120: periodic local polls and fetches stop, while filesystem-watcher refreshes still land and a once-per-second heartbeat renders their results, so the display keeps tracking real changes), and deep sleep (detached session, background window, or zoomed away: everything stops, and watcher events are dropped or deferred). Waking refreshes immediately: the local poll fires at once, a root-directory change that happened while hidden is replayed, and the frame repaints; the fetch timer instead resumes on its normal cadence so switching to a pane never triggers a burst fetch of every repo. With many long-lived gitpane instances only the one on screen does any work, which cuts idle CPU (and battery) from a constant 15-20% per hidden instance to zero. Outside tmux behavior is unchanged; opt out with watch.sleep_when_hidden = false.
Changed
The tick, local-poll, and fetch timers now skip missed ticks instead of replaying them in a burst after the event loop stalls.
rwhich: bound prefix_len in directory dictionary parsing
The front-compressed 'N suffix' lines come from untrusted repository
data; a hostile filesite could set N larger than the previous
directory, making memcpy(dir, prev, N) read out of bounds. Clamp N
to the actual previous directory length in both the exact and the
glob parsers.
fetch: avoid infinite loop when FETCH_RETRY=0
retry was decremented to -1 and neither 'retry > 0' nor a
'retry <= 0' exit was taken, so the failover loop spun forever.
Clamp max_retry to >= 0 and break out of the loop when no retry
budget remains.
pkg_audit: enforce extract limit on total, not per member
The size limit check compared nread against max_size - extracted where
extracted is accumulated across all archive members, so a malicious
archive with many small members could exceed the limit by the sum of
all members while each individual chunk check passed. Check the
declared entry size against the remaining budget up front.
