[SLP]Recalculate copyable-element deps after tree reordering
Reordering permutes the operand columns of the entries and may move an
operand between copyable-covered and plain edges, making the computed
dependency counts stale and tripping the unscheduled-deps assertion.
Reviewers:
Pull Request: https://github.com/llvm/llvm-project/pull/216410
pci: Do not reconcile MPS across PCI domains
A PCI function can provide a host bridge into a synthetic PCI domain.
Intel VMD does this: the host facing VMD function remains in its
original domain while the hidden Root Ports and endpoints appear in a
separate domain. The VMD function's Device Control does not describe
an upstream link in that synthetic hierarchy.
The hierarchy wide cold pass incorrectly used the VMD function's MPS
to reprogram the hidden ports and their endpoints. Stop both cold
reconciliation and runtime path walks at a PCI domain boundary. The
real Root Ports within the VMD domain continue to reconcile their
endpoints normally.
Reviewed by: imp
Tested by: Michael Butler <imb at protected-networks.net>
Fixes: 8e9fe9996a1f ("pci: Reconcile MPS before attaching PCIe devices")
MFC after: 6 days
Sponsored by: BBOX.io
Differential Revision: https://reviews.freebsd.org/D58837
[CIR] Test bit-field access units split by register size
A span of bit-fields wider than one register splits into two access units, each
marked on its own. Nothing covered that path: every bit-field in these tests is
24 bits or narrower, and the splits already covered come from a zero-length
bit-field instead.
Two of the three cases are worth having for a reason beyond coverage. When a
record carries both a data unit and an empty one it is not ABI-empty either way,
so the differential assert cannot see a wrong mark on an individual unit, and
these checks are the only thing that can.
Assisted-by: Cursor / claude-opus-5
pkg-vulnerabilities: CVE-2025-69720 was fixed in ncurses-6.6
According upstream NEWS it was fixed in 20251213 and 6.6 was released
on 20251230.
Reported via PR pkg/60589 from Showta Ishizaki, thanks!
vnode(9): Split a wall of prose into an itemized description list.
Prompted by puzzling over the obtuse API contract around v_writecount
and VOP_OPEN/CLOSE for:
PR kern/60586: panic after hot-plugging raidframe component
[clang][WebAssembly] Remove `OPT_no_pthread` handling (#216378)
`-no-pthread` was originally added to Clang in 425b1a5106def (D11087)
simply to prevent "unknown argument" errors when building winpthreads in
mingw-w64.
It was subsequently used in `WebAssembly.cpp` when thread options were
made consistent in 9d5a089bf544e (D57874) via `Args.hasFlag`.
No other Clang toolchains handle `OPT_no_pthread` (they all use
`Args.hasArg(options::OPT_pthread)`), and `-pthread` is not typically
treated as a negatable boolean option in GCC/Clang drivers.
Align WebAssembly with all other Clang toolchains by removing the
`OPT_no_pthread` check.
NAS-142185 / 27.0.0-BETA.1 / Fix stale literalinclude path in docs/database/sqlalchemy.rst (#19505)
A prior commit (PR #18854) split plugins/api_key.py into a package
(api_key/{__init__,crud,internal}.py), moving APIKeyModel into crud.py.
The docs literalinclude still pointed at the old single-file path, which
no longer exists, breaking `make html` (SPHINXOPTS=-W treats the
resulting warning as fatal).
ca-certificates: Update to 20260601
ca-certificates (20260601) unstable; urgency=medium
* Remove ca-certificates-local example (closes: #988912, #1127101).
* Update Mozilla certificate authority bundle to version 2.86
The following certificate authority was added (+):
+ e-Szigno TLS Root CA 2023
The following certificate authorities were removed (-):
- QuoVadis Root CA 2
- QuoVadis Root CA 3
- DigiCert Assured ID Root CA
- DigiCert Global Root CA
- DigiCert High Assurance EV Root CA
- SwissSign Gold CA - G2
- SecureTrust CA
- Secure Global CA
- COMODO Certification Authority
- Certigna
[18 lines not shown]
pthread_create(3): fix dead references to racct(2)
As far as I can tell, racct(2) has never existed, not even when
I added these references a decade ago.
Change them as commit e9e615c88a74 did in thr_new(2).
Reported by: Karlo Miličević <karlo98.m at gmail.com>
[analyzer] Only underline the exact parameter that is bound to the return value in UseAfterLifetimeEnd (#215651)
Currently the `UseAfterLifetimeEnd` checker highlights always the first
argument that is annotated with the `[[clang::lifetimebound]]`
annotation. Like:
```text
temp.cpp:5:31: note: Value's lifetime bound to the lifetime of 'y' here
4 | int x = 1, y = 2;
| ~~~~~~~~~~~~~~~~
5 | return multi_param_test_ref(x, y);
| ^
```
As seen even when checker correctly notes that the value's lifetime is
bound to the lifetime of the `y` parameter, it incorrectly highlights x
since that is the first annotated parameter. In order to fix this I have
added a logic which checks which annotated parameter's region is bound
to the return's region and do the highlight based on that.
[16 lines not shown]
[HLSL][longvec][Tablegen] Use templates to define Vector api's larger than 4 (#216143)
resolves #216139
resolves #216140
This change adds a templatized vector emitter to TableGen's HLSLEmitter.
We add tests for the tablegen and confirm we did it right by
implementing the abs api.
Assisted by GPT-5.6 sol via co-pilot
[CIR] Address more reviewer feedback
Remove droppedFieldHoldingData. The differential asserts allow for an error
having already been reported instead, which covers any NYI in record lowering
rather than just the one.
Mark a bit-field access unit by promoting its storage member when a named
occupant is emitted, rather than pre-scanning the unit first. Both bit-field
paths now do it the same way, and the unit's fields are walked once.
Rename runStorageIdx to storageIdx.
Assisted-by: Cursor / claude-opus-5
[DWARFLinker] Constrain a function's high_pc to its own symbol (#215952)
Mach-O objects built with .subsections_via_symbols make every symbol an
independently placeable atom, and the linker packs atoms without
preserving the spacing they had in the object file.
I have an example where the compiler describes such a subprogram as
extending past its own atom. While it's debatable whether that's a good
idea, it's not invalid in the object file. However, once linked, it is
invalid.
We can make dsymutil resilient against this by looking at the size of
the symbol in the debug map and adjusting the end_pc. I'm doing so
conservatively so that only a collision is repaired. Already
overlapping/invalid ranges remain untouched.
rdar://184768778
arm64: close a race in SVE register management
While testing an unrelated pmap change, D58708, that dramatically
reduces the number of TLBI instructions performed, and likely the
timing of unrelated events, I started seeing "Storing an invalid VFP
state" panics in vfp_save_state_common(). However, the origin of this
panic is elsewhere, in the else branch of sve_restore_state().
Specifically, my pmap change seems to have increased the likelihood that
the thread executing the else branch would be preempted by another
thread between the critical_exit() inside the else branch's call to
vfp_restore_state_common() and its own call to critical_enter(). Prior
to expanding the scope of the else branch's critical section, the MPASS
added by this change would fire, catching the problem at its source,
rather than later in vfp_save_state_common().
Assisted-by: Claude Code (Opus 5)
Reviewed by: kib, markj
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D58723
[LV] Simplify the latch branch before rewriting ALM for a scalar VF (#216257)
Run simplifyBranchConditionForVFAndUF before replaceMaskWithCompare
before, so the simplification triggers before replaceMaskWithCompare
writes the plan.
PR: https://github.com/llvm/llvm-project/pull/216257
Add an applicability engine for alerts
This commit adds changes to give alerts a way to state which systems they are meaningful on in terms of two independent axes, hardware class and license, instead of the conflated product_type predicate they lean on today. The engine is pure and delegates the HA question to the entitlement policy so there stays one definition of it in the tree.
Nothing declares the new applies_to/listed_when slots yet and no enforcement point reads them, so this is inert on its own; the declarations and the call sites follow.
Only report a missing license on HA capable systems
This commit fixes an issue where an unlicensed R-series or Z-series started getting told to contact support about a license it was never sold. Those chassis are appliances so they satisfy the hardware rule, but they cannot fail over, and on 26 the product_type disjunct meant a system with no license only reached this alert when it was HA capable. HA capability is a chassis probe the applicability axes deliberately do not carry, so the test sits in check_sync rather than in applies_to.
