[Clang] Restrict ClangScanDeps darwin-specific test not to run in cross-compile (#213884)
The test added in 316a29603228c5d5000e0ddf8dfba2a494ac7ee9 fails when
run on MacOS but targeting Linux as a cross compiler.
igc: stability improvements
Always disable PCIe ASPM for i226 type cards to improve stability and wire sysctl calls to iflib_request_reset instead of igc_if_init as this will stall the drivers RX path.
pci: Add L1 PM definitions
Add register/bit definitions for the L1 PM substates capability
(PCIZ_L1PM) to pcireg.h.
Signed-off-by: Michael Adler <madler at tapil.com>
pharo-vm12: Add pharo-vm12-12.0.3-beta
This repository contains the code of the Pharo Virtual Machine. This
implementation started as a fork of OpenSmalltalk-VM. The current
project would not have been possible without all their previous work.
The current implementation has the following core features:
- an indirect threaded bytecode compiler using GNU extensions
- a generational scavenger garbage collector: a semi-space + nursery
for the young generation, and a mark-compact collector for the old
generation
- a space for permanent objects that do not need to be scanned by the
GC
- a baseline JIT compiler that
- translates primitive operations using IR templates
- translates bytecode methods using a simple abstract interpretation
approach to reduce memory pressure (fewer loads/stores)
- FFI through the well-known libFFI, and support for non-blocking FFI
[3 lines not shown]
gmsh: Add gmsh-4.15.2
Gmsh is an open source 3D finite element mesh generator with a
built-in CAD engine and post-processor. Its design goal is to provide
a fast, light and user-friendly meshing tool with parametric input and
flexible visualization capabilities. Gmsh is built around four modules
(geometry, mesh, solver and post-processing), which can be controlled
with the graphical user interface, from the command line, using text
files written in Gmsh's own scripting language (.geo files), or
through the C++, C, Python, Julia and Fortran application programming
interface.
kicad-*: Update to 10.0.5
KiCad 10.0.5 (2026-07-22)
The 10.0.5 stable version contains critical bug fixes and other minor
improvements since the previous release.
A list of all of the fixed issues since the 10.0.5 release can be
found on the KiCad 10.0.5 milestone page.
KiCad 10.0.4 (2026-06-21)
The 10.0.4 stable version contains critical bug fixes and other minor
improvements since the previous release.
A list of all of the fixed issues since the 10.0.4 release can be
found on the KiCad 10.0.4 milestone page.
pci: Add L1 PM definitions
Add register/bit definitions for the L1 PM substates capability
(PCIZ_L1PM) to pcireg.h.
Signed-off-by: Michael Adler <madler at tapil.com>
[mlir][SPIR-V] Verify ExecutionMode operand count and kind (#212828)
Add a verifier for spirv.ExecutionMode enforcing the correct number of
literal operands per execution mode and rejecting `<id>`-only modes and
share the operand schema with spirv.ExecutionModeId
fix p9fs_vget_common() panics
This addresses a race when two vnodes attempt to call vfs_hash_insert(),
but only one succeeds. Also, in case of an error from
p9fs_reload_stats_dotl(), it marks the vnode for deletion.
Reviewed by: kib
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D58632
[AMDGPU] Limit register pressure of pipelined loops
Opt AMDGPU into the generic MachinePipeliner register-pressure detector via
shouldLimitRegPressure(), and supply an occupancy-aware verdict in
isScheduleRegPressureTooHigh(): reject a schedule whose SGPR or VGPR/AGPR
pressure would drop the kernel below its target occupancy, or exceed a
register class's addressability cap. On gfx90a+ VGPRs and AGPRs share one
register file, so their combined footprint is bounded together. These match
the limits GCNSchedStrategy enforces.
igc: stability improvements
Always disable PCIe ASPM for i226 type cards to improve stability and wire sysctl calls to iflib_request_reset instead of igc_if_init as this will stall the drivers RX path.
nfs_commonkrpc.c: Get rid of NFSv4.0 delegation cruft
Delegations in NFSv4.0 never worked well and, since
the NFSv4.0 protocol is now deprecated, use of delegations
for NFSv4.0 is disabled as far as the client can do so.
It turns out that some Illumos NFSv4.0 server issues
delegations anyhow (even when the callback path is
specified as 0.0.0.0) and this can cause use after free
problems.
This patch deleted some cruft that did an nfsrpc_openrpc()
call recursively when an NFSv4.0 server failed to issue
a delegation when it had previously done so.
This code was only meant to be an optimization and
would have been rarely exercised. Since this recursive
call of nfsrpc_openrpc() is in some of the backtraces
in the bugzilla PR, getting rid of the cruft makes sense.
[5 lines not shown]
Consolidate the managed-dataset registries and guard every mutator
## Problem
Five separate registries answered "is this a dataset middleware manages?", with four different membership sets and no shared matching rule, and they had drifted apart: `<pool>/ix-applications` was creatable and then permanently invisible because one carried a trailing slash the others lacked, and the replication registry did not know about the apps datasets at all. Two of the five matched by substring, which confiscated names the user is entitled to -- `<pool>/ix-apps-data` and `<pool>/.systembackup` were hidden from `pool.dataset.query` forever, and therefore unmanageable, since `get_instance`, `update` and `delete` all run through that listing.
Protection had holes in both directions. `exclude_internal_datasets` was reachable from the wire through `pool.dataset.query`'s free-form `extra` dict, where the model's `extra="forbid"` never reaches, so anyone holding `DATASET_READ` could enumerate the boot pool and the system dataset. And eleven public entry points had no protection at all: `pool.dataset.promote`, `rename`, `set_quota`, `get_quota`, `lock`, `change_key` and `inherit_parent_encryption_properties`, the three `zfs.tier` mutators, and `pool.snapshot.rename` -- which was broken for every valid input in any case, since it passed a snapshot id to a method that rejects any name containing `@`.
## Solution
- **One module, one predicate per question.** `utils/zfs/managed_datasets.py` replaces all five registries. Every predicate matches the same way -- compare the component directly below the pool root against a name, exactly, with the boot pools matched at component zero instead -- so where two of them disagree it is because they manage a different set of names, and that is product policy you can read in one line.
- **The substring reach is gone.** `<pool>/ix-apps-data`, `<pool>/.systembackup` and `<pool>/foo/.system` are visible, creatable, updatable and deletable again, and their destruction publishes an event. That last one was not cosmetic: the suppressed branch is what clears the destroyed dataset's encryption key from the database and removes it from the other HA node, so an out-of-band `zfs destroy` used to leave the key registered on both nodes and in KMIP.
- **The one override a caller could reach is off the wire.** `exclude_internal_datasets` moves onto a new private `pool.dataset.query_impl`, so whether the managed datasets are listed is a property of the caller rather than of the request.
- **Guards live at the chokepoint where there is one** -- inside the `@private` implementation rather than at each public method -- because a missing guard at a public boundary fails open and silently, while a missing owner opt-in fails closed and loudly inside that owner's own workflow. Guarding `update_impl` and `unload_key` took the `bypass=True` call sites from sixteen to thirty-four; the new ones sit on pool import, the system dataset, audit, docker and the container migration. The six operations with no chokepoint to pass through are guarded at the public method instead.
- **Gaps closed.** All eleven unguarded entry points now refuse managed datasets, `rename` refuses a managed *destination* so a dataset can no longer be created at a protected name, `delete` reports `EACCES` rather than a misleading `EINVAL`, and `pool.snapshot.rename` is routed at the snapshot rename endpoint and works. `mount`, `unmount` and `replication.create_dataset` are deliberately left unguarded, with the reasons recorded where they sit.
[libc++] Tweak comments for workaround about `fpclassify` overloads (#212388)
Explaining why we have `_LIBCPP_PREFERRED_OVERLOAD` and template
versions.
mlterm: pull upstream window handling fixes
Fix a 3.9.5 regression that sets window manager hints on child windows.
Also move input focus handling for multiple input windows from FocusIn
to WM_TAKE_FOCUS.
Bump PKGREVISION.
[AArch64][Windows] Fix swift async context slot placement (#212922)
Swift async functions can miscompile on Windows ARM64 at `-O2`, when
there's enough register pressure that a local gets scavenged into the
callee-save area: the local ends up sharing an address with the saved
caller x29, so the epilogue restores a value the function has already
overwritten. swiftlang/swift#90920 has a reduced repro.
`assignCalleeSavedSpillSlots` creates the swift async context object
before the callee-save loop instead of inside it next to the FP slot.
MachineFrameInfo ends up with it above the frame record while the
prologue stores it below at FP-8, and the 8 byte disagreement leaves a
hole in the middle of the callee-save area. PEI's scavenger hands that
hole to the local. Only reproduces at -O2 and up since scavenging is
gated on the opt level.
```
sub sp, sp, #112
str x19, [sp, #16] // 8-byte Spill
[22 lines not shown]
