[clang][P2719] Relax requirements for matching operator new and delete
The most recent revision of P2719 introduced very strict rules about
matching parameter sets between type aware operators new and delete.
The intention was to resolve the classic "no matching operator delete
has been found so the object will silently leak" problem. The strict
rules however made deleting objects that had a placement new
"impossible".
I missed this however as all of our large scale tests involved
projects that were already using manually implemented allocators
(often trying to support type isolation). The problem with this from
a validation point of view is simple: all of these projects had
existing class scoped operators, and the untyped delete was silently
selected, avoiding the need for a non-placement type-aware delete
that would conflict with the placement cleanup delete.
The next revision of P2719 resolves this by removing the exact type
[6 lines not shown]
nfs_pub: move from vfs_subr.c to vfs_export.c
nfs_pub is used only in vfs_export.c.
Reviewed by: kib, rmacklem
Differential Revision: https://reviews.freebsd.org/D56777
[mlir][SPIR-V] Add Weak linkage type and SPV_AMD_weak_linkage extension (#195660)
- add 'Weak' linkage type (SPV_AMD_weak_linkage)
- deduce the Linkage capability and linkage-type extension from
linkage_attributes in UpdateVCE pass
---------
Co-authored-by: Jakub Kuderski <kubakuderski at gmail.com>
[PGO][ICP] Prevent indirect call promotion to functions with incompatible target features (#192142)
Profile-driven indirect call promotion was promoting indirect calls to
functions requiring advanced CPU features (e.g., AVX512) even when the
caller function did not support those features. When these promoted
calls were subsequently inlined, it could lead to invalid IR and
backend crashes during instruction selection because the target CPU
could not handle the advanced instructions.
This patch addresses the issue by adding a target feature
compatibility check to `llvm::isLegalToPromote` in
`CallPromotionUtils.cpp`. If the callee requires target features
(prefixed with `+`) that are not present in the caller's target
features, the promotion is skipped. By centralizing this check in
`isLegalToPromote`, we protect all passes relying on this utility
(such as `SampleProfileLoader` and `IndirectCallPromotion`) from
promoting to incompatible targets. This also prevents incorrect
inlining of `always_inline` functions that would otherwise be promoted
via indirect calls and then inlined.
[3 lines not shown]
py-zope.proxy: updated to 7.2
7.2 (2026-04-30)
- Add support for automatically building and publishing Windows/ARM64 wheels.
- Add support for automatically building and publishing source distributions.
[MLIR] Add HasAncestor op trait (#195447)
Add HasAncestor/AncestorOneOf traits that verify an operation has a
specific ancestor anywhere in the parent chain, unlike HasParent which
only checks the immediate parent.
py-dulwich: updated to 1.2.1
1.2.1 2026-04-29
* Derive the LFS endpoint as the remote's on-disk LFS store
(``<remote>/.git/lfs`` for worktrees, ``<remote>/lfs`` for bare repos)
when ``remote.origin.url`` points at a local filesystem path or
``file://`` URL, matching git-lfs behaviour. Previously the built-in
smudge filter constructed an HTTP-style ``<remote>.git/info/lfs`` path
that did not exist on disk, leaving LFS-tracked files as pointers when
cloning from a local repo.
* Deduplicate objects when writing a multi-pack-index. Objects present
in multiple packs (e.g. after ``git gc`` creates a cruft pack) would
otherwise produce an OIDL chunk with repeated SHAs, causing ``git
multi-pack-index verify`` to fail with "oid lookup out of order".
* Extend ignorecase and precomposeunicode support to index lookups.
18086 viona does not offer IPv6 TSO flags
Reviewed by: Andy Fiddaman <illumos at fiddaman.net>
Reviewed by: Ryan Zezeski <ryan at zinascii.com>
Approved by: Robert Mustacchi <rm at fingolfin.org>
Make sure the start and end of the PT page ranges are aligned to the
size of what's addressable by a single PT page, thus ensuring we count
them up correctly.
bsdinstall: Always use pkg.FreeBSD.org
The FreeBSD-base bits are accessible via pkg.FreeBSD.org, even for
releases, so there is no need to point at pkgbase.FreeBSD.org.
MFC after: 3 days
ccache: updated to 4.13.6
Ccache 4.13.6
Bug fixes and improvements
Fixed a potential manifest/result cache key collision in MSVC depend mode when compiling a source file with no included files.
Improved robustness when parsing cache entry data structures.
Test improvements
Changed the remote_helper test suite to skip gracefully when the storage test helper is unavailable, avoiding failures when testing a system-installed ccache.
[orc-rt] Change SPS controller-interface naming conventions. (#195614)
This commit makes two changes to the naming conventions for SPS CI
symbols:
1. The orc_rt_sps_ci_ prefix is replaced with orc_rt_ci_sps_ (for SPS
wrapper functions) and orc_rt_ci_ (without the "sps_" suffix) for data
symbols.
2. The _sps_wrapper suffix is dropped from wrapper functions, since the
prefix now distinguishes between SPS-wrappers and data symbols.
