[M68k] Fix Instruction Verifier errors related to `MOVEM` and `PHI` lowering (#219011)
This fixes some errors reported by the Instruction Verifier when
building with `-verify-machineinstrs`.
- The `MOVM` pseudos are given an 8-bit variant so that the IV can
correctly see 8-bit physical registers being defined/used. Without this,
8-bit register spills fail IV by attempting to load/store an undefined
physical register (the 16-bit superclass of the 8-bit register). Codegen
is not affected by this change.
- During `CollapseMOVEMPass`, the implicit ops are now copied over from
the old deleted instructions into the new combined instruction. This
fixes IV failing in cases where an instruction wants to use registers
that were defined by the collapsed `MOVEM`. Codegen is not affected by
this change.
- CCR is now marked as non-allocatable (which is true anyway). The
custom inserter for `CMOV` (`emitLoweredSelect()`) has logic where CCR
is added as a live-in for the newly-created blocks that are expected to
use it. This would cause IV to fail, because IV doesn't allow non-entry
[3 lines not shown]
workflow/release-binaries: Hard-code Wix install path (#219328)
Searching for the candle.exe executable is very slow and we know the
install path will always be the same since we have version pinned the
install.
[LV] Remove dead attachRuntimeChecks call for the epilogue plan (NFC). (#219575)
The runtime check blocks are attached to the main plan, and executing it
gives them predecessors in the generated IR. attachRuntimeChecks only
attaches check blocks without predecessors, so the call for the epilogue
plan never does anything. Remove it.
[CIR][NFC] Add tests for Vector of bool in GV, Shuffle (#218135)
Add extra tests for a vector of booleans in the global variable with
zero attr, shuffle, and dynamic shuffle
Query pc-sysinstall directly and drop the forked backend scripts
src/backend-query held a copy of pc-sysinstall's query scripts that had
drifted from the originals, so a fix in pc-sysinstall did not reach the
installer and the two disagreed about what a disk looked like. Call
pc-sysinstall itself and delete the fork.
partition.py now goes through query_backend(), which runs a
pc-sysinstall subcommand and returns its output. parse_entities()
splits the 'name-field: value' lines that disk-part and part-label
emit into one dict per partition or gap. pc-sysinstall writes those
lines in on-disk order and dictionaries keep insertion order, so the
result preserves the physical layout of the device without sorting it
back into place. Free space keeps the 'freespaceN' names the old
scripts used, so callers read the same as before. disk-info uses
'field=value' instead and gets its own pattern.
data.py loses the query prefix and setup.py stops installing the
scripts into lib/install-station/backend-query.
[AMDGPU] Code clean up and denorm check removal for bf16 omod folding (#219042)
This is the follow-up PR to address the additional comments and
suggestions from https://github.com/llvm/llvm-project/pull/218286
Use FP64FP16Denormals to check the output denomal flushing because
BF16 is usig the default.
Also clean up the surrounding code:
- src0_modifiers/src1_modifiers are always present on these packed
opcodes (VOP3P_Profile sets HasModifiers), so drop the null checks and
dereference the operands directly.
- Fix the comment on the modifier check: rather than "modifiers other
than op_sel_hi block folding", the point is that when omod is applied to
a packed instruction it only applies to the low half of the input and
output.
[2 lines not shown]
Disable diskid and gptid GEOM labels on the live media
kern.geom.label.disk_ident and kern.geom.label.gptid default to enabled,
so GEOM tastes a raw disk twice and adaX coexists with
diskid/DISK-<serial>. When a diskid-derived provider is opened for
exclusive write, such as by an imported pool, GEOM withdraws the raw
partition geom for the whole disk. gpart(8) then fails on that disk and
its partition device nodes disappear.
kern.disks still reports the raw name, so the installer enumerates the
disk, gets nothing back from gpart, and offers a live pool as free
space. Disabling both labels on the live kernel keeps enumeration on raw
names and also lets the installer read disks that are already in this
state from an earlier install or a dual-boot setup.
[flang][OpenMP] Track reachable metadirective paths
Semantic checks currently consider each statically applicable replacement
independently. This can diagnose lower-ranked replacements that selection can
never reach. It also prevents nested construct selectors from observing
directives selected by enclosing metadirectives.
Consider an enclosing dynamic metadirective and a nested selector:
```text
outer: when(flag: target) default(parallel)
inner: when(construct={parallel}: simd) default(nothing)
```
The enclosing selection creates mutually exclusive effective paths:
```text
enclosing metadirective
/ \
[39 lines not shown]
sun4v: Add xhci(4) to sparc64 GENERIC config.
Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller is
present in SPARC S7-2 servers (device id 0x8241).
Not tested yet.
Revert "ciss: Add max physical target"
This reverts commit 45645518ea19ccb4761aee3a525aab2f323d37d4.
Although this changed looks like it should just be a harmless change to
bookkeeping, it turns out that it changes the termination condition of
the initial device scan, resulting in it never finishing. This causes
the boot to hang forever coming up. Since I don't have good access to
hardware, I'm reverting until the exact details can be sorted out.
Reported by: Edward Scroop
Sponsored by: Netflix
MFC After: 1 week
(cherry picked from commit ba9aaed01a484778f1c1f2fb5d7e30dbb1a8f5ad)
www/phpbb3: update to 3.3.17
3.3.14 is affected by CVE-2026-29199 (CVSS 8.1): with force_server_vars
disabled, phpBB builds the password reset link from the HTTP Host
header,
so an attacker who can control that header makes reset mails point to a
domain of their choice, which may lead to account takeover.
Also fixed since 3.3.14: improper state verification in the OAuth
implementation (SECURITY-293), IDOR when composing private messages
(SECURITY-286), CSRF on report submission (SECURITY-287), cross-user
notification read state manipulation (SECURITY-290) and HTML generation
from page data (SECURITY-283).
Changelog:
https://github.com/phpbb/phpbb/blob/release-3.3.17/phpBB/docs/CHANGELOG.html
Security: CVE-2026-29199
Security: 4d06b948-a323-11f1-a655-3497f65b111b
MFH: 2026Q3
[3 lines not shown]
www/phpbb3: update to 3.3.17
3.3.14 is affected by CVE-2026-29199 (CVSS 8.1): with force_server_vars
disabled, phpBB builds the password reset link from the HTTP Host
header,
so an attacker who can control that header makes reset mails point to a
domain of their choice, which may lead to account takeover.
Also fixed since 3.3.14: improper state verification in the OAuth
implementation (SECURITY-293), IDOR when composing private messages
(SECURITY-286), CSRF on report submission (SECURITY-287), cross-user
notification read state manipulation (SECURITY-290) and HTML generation
from page data (SECURITY-283).
Changelog:
https://github.com/phpbb/phpbb/blob/release-3.3.17/phpBB/docs/CHANGELOG.html
Security: CVE-2026-29199
Security: 4d06b948-a323-11f1-a655-3497f65b111b
MFH: 2026Q3
Sponsored by: Netzkommune GmbH
UPDATING: Fix entry for getgroups(2)/setgroups(2)
Fix a typo, grammar, and generally rephrase for better clarity.
Fixes: 3463f02706db ("UPDATING: add an entry for [gs]etgroups")
MFC after: 1 day
MFC to: stable/15
Sponsored by: The FreeBSD Foundation
(cherry picked from commit b7cff2a8c47eb09968430e53cab8b05cf8897d3f)
Add middleware support for LIO ALUA HA
Wire up the middleware side of LIO ALUA high-availability: load
lio_ha.ko with per-node addresses on service start, manage ALUA
state across failover events, clean up STANDBY configfs on pool
export, and add pre-flight validation that targets have static
initiator ACLs before ALUA can be enabled.
For each target, create a portal-less phantom TPG carrying the peer
node's controller group so that a single RTPG response from any
connected port lists both ALUA groups. Write tpgt_N/rtpi explicitly
before enable so that relative target port IDs in RTPG match the
tag formula (portal.tag on Node A, portal.tag + 32000 on Node B)
rather than being auto-assigned sequentially by the kernel.
ALUA group states are driven by role and ha_state:
MASTER + synced local=OPTIMIZED remote=NONOPTIMIZED
MASTER + connected local=OPTIMIZED remote=TRANSITIONING
[4 lines not shown]
