net/rsync: drop py-cmarkgfm build dep, fix inert path substitutions
Drop python and py-cmarkgfm from the BUILD_DEPENDS: The tarball ships
pre-rendered nroff man pages, so the upstream md2man toolchain is not needed.
While here, fix a post-patch REINPLACE_CMD pattern that has been silently
inert since 2022 (PR 263787): Replace with two correct substitutions so the
installed man pages reference ${ETCDIR} instead of /etc/rsync*.
Bump PORTREVISION because installed man page content changes.
Sponsored by: Netflix
[C++ Safe Buffers][libcxx][test] Add a test for hardened span in ObjC++
The C++ Safe Buffers project does not officially support ObjC++, while
people may still want to apply the analysis to ObjC++ code for
improved confidence. However, it would be meaningless to do so if
hardened containers do not trap out-of-bounds accesses. We need to add
a test that shows that hardened containers do work for ObjC++.
rdar://180461846
Convert nginx proxy forwarding to AF_UNIX
This commit changes our proxy settings for nginx to send to
a dedicated AF_UNIX socket to more precisely delineate nginx
originating connections and localhost ones.
Merge tag 'x86-urgent-2026-06-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 fix from Ingo Molnar:
- Prevent NULL dereference on theoretical missing IO bitmap (Li
RongQing)
* tag 'x86-urgent-2026-06-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
x86/ioperm: Prevent NULL dereference on theoretical missing IO bitmap
ntsync.4: add the man page
Reviewed by: ziaee
Discussed with: Alex S <iwtcex at gmail.com>
Sponsored by: The FreeBSD Foundation
MFC after: 3 days
Differential revision: https://reviews.freebsd.org/D57659
[flang][OpenMP] Fix ICE lowering user-defined operator declare reduction
A REDUCTION clause naming a user-defined operator (e.g.,
reduction(.myop.:x)) crashed in lowering: ReductionProcessor assumed the
DefinedOperator clause variant always held an intrinsic operator and called
std::get<IntrinsicOperator> unconditionally, which aborts for the
DefinedOpName alternative.
Handle DefinedOpName in the reduction clause processor, adding the
clause-side counterpart to the directive handling from #190288. For a
locally declared user-defined operator reduction, resolve the operator to
its reduction symbol and reference the omp.declare_reduction op materialized
for the declare reduction directive. The op name is now module-scoped via
AbstractConverter::mangleName, on the directive and clause sides in
lockstep, so reductions with the same operator spelling in different modules
no longer collide.
Cases that are not yet supported (reductions imported by USE association,
renamed or merged operators, and declarations with multiple types) now emit
[10 lines not shown]
[Github] Reenable prune-unused-branches workflow
The Github API has recovered and the previous failure mode has been
rectified by ensuring that branches are ready for deletion for seven
days rather than 24 hours.
Reviewers: cmtice
Reviewed By: cmtice
Pull Request: https://github.com/llvm/llvm-project/pull/205439
Merge tag 'timers-urgent-2026-06-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull misc timer fixes from Ingo Molnar:
- Fix timekeeping locking order bug in the timekeeping init code
(Mikhail Gavrilov)
- Fix u64 multiplication bug in the posix-cpu-timers code on 32-bit
kernels (Zhan Xusheng)
- Fix macro name in comment block (Ethan Nelson-Moore)
- Fix off-by-one bug in the compat settimeofday() usecs validation code
(Wang Yan)
* tag 'timers-urgent-2026-06-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
time: Fix off-by-one in compat settimeofday() usec validation
hrtimer: Correct CONFIG_NO_HZ_COMMON macro name in comment
posix-cpu-timers: Use u64 multiplication in update_rlimit_cpu()
timekeeping: Register default clocksource before taking tk_core.lock
15.1R: Use native redirect instead of duplication
This will reduce maintenance burden going forward, also it serves to
demonstrate that we can trivially implement redirects in the tree vs
doing other things that are more labor intensive.
Differential Revision: https://reviews.freebsd.org/D57792
[Github] Make prune-unused-branches only delete branches after 7 days
To hopefully prevent the last failure mode that led to the job being
disabled where the GitHub API failed to return results for >24 hours.
Reviewers: cmtice
Pull Request: https://github.com/llvm/llvm-project/pull/205438
Merge tag 'smp-urgent-2026-06-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull misc CPU hotplug fixes from Ingo Molnar:
- Fix CPU hotplug error handling rollback bug (Bradley Morgan)
- Fix possible output OOB write bug in the sysfs hotplug states
printing code (Bradley Morgan)
* tag 'smp-urgent-2026-06-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
cpu: hotplug: Bound hotplug states sysfs output
cpu: hotplug: Preserve per instance callback errors
fusefs: fix two intermittency bugs in the destroy tests
* Though undocumented, statfs(2) can sometimes return EBADF or ENOENT
while an unmount is in progress.
* In MockFS::write_response, write(2) may fail if m_fuse_fd has already
been closed. This doesn't happen in the normal sequence of events,
but it can happen if some process unrelated to the test nosily decides
to access the test file system while it's being unmounted.
PR: 296237
Reported by: siva
MFC after: 2 weeks
Sponsored by: ConnectWise
Reviewed by: siva
Differential Revision: https://reviews.freebsd.org/D57787
[Hexagon] Add HVX caller-save remark pass for call-site diagnostics (#189188)
Add a new MachineFunctionPass (HexagonHVXSaveRemark) that emits
optimization analysis remarks when HVX vector registers must be saved
and restored around function calls. All HVX registers are caller-saved
(Section 5.3 of the Hexagon ABI), so any HVX value live across a call
requires a save/restore pair on the stack. Each HVX vector is 64 or 128
bytes, making this overhead expensive.
The pass exits when remarks are not requested
(-Rpass-analysis=hexagon-hvx-save) or when HVX is not enabled. A byte
threshold (default 1024, tunable via -hexagon-hvx-save-threshold)
filters out functions with only a small number of saves. The remarks
help programmers identify call sites where inlining, hoisting, or
sinking could reduce the save/restore cost.
mail/fetchmail{,conf}: Update 6.6.4 => 6.6.5 (vulnerability fix)
Fetchmail 6.6.5 is the sixth fetchmail 6.6 release on 2026-06-17, it
fixed a buffer sizing bug in the RPA code that could crash fetchmail
due to a buffer overrun when long user names and service realm and
challenges were used, POP3 was used, the username contained
@compuserve.com and the server would offer a non-standard
"AUTH"-without-arguments request that would list RPA
(case-insensitively) as supported authentication option.
Changelog:
https://sourceforge.net/projects/fetchmail/files/branch_6.6/
Improve mail/fetchmailconf:
- Replace PORTVERSION with DISTVERSION.
- Fix antipattern "BUILD_DEPENDS=RUN_DEPENDS".
- Fix warnings from portclippy.
PR: 296204 283227
[6 lines not shown]
backout to libplacebo-7.351.0, there are various issues looking like
memory corruption with 7.360.1, some fixed in newer git head but tb@
ran into another one there too. reported by Walter Alejandro Iglesias
and tb, replicated here with repeated plays of a short mkv, typically
within 20 attempts, often less (seem more common with vaapi, but does
happen without too). ok tb brad
[lldb] Resolve dyld introspection SPIs with dlsym (NFC) (#205434)
HostInfoMacOSX's SharedCacheInfo used the dyld process-snapshot
introspection SPIs only when <mach-o/dyld_introspection.h> was present,
gating the calling code behind a compile-time macro.
To avoid bifurcating the behavior based on the SDK, rather than the
presence of the symbols, use dlsym to resolve them at runtime.
While here, fold the duplicate dlsym of dyld_image_segment_data_ into
the new, once-initialized, shared table.
Assisted-by: Claude
Merge tag 'locking-urgent-2026-06-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull locking fix from Ingo Molnar:
- Fix the incorrect RCU protection in rt_spin_unlock() (Thomas
Gleixner)
* tag 'locking-urgent-2026-06-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
locking/rt: Fix the incorrect RCU protection in rt_spin_unlock()
mail/fetchmail{,conf}: Update 6.6.4 => 6.6.5 (vulnerability fix)
Fetchmail 6.6.5 is the sixth fetchmail 6.6 release on 2026-06-17, it
fixed a buffer sizing bug in the RPA code that could crash fetchmail
due to a buffer overrun when long user names and service realm and
challenges were used, POP3 was used, the username contained
@compuserve.com and the server would offer a non-standard
"AUTH"-without-arguments request that would list RPA
(case-insensitively) as supported authentication option.
Changelog:
https://sourceforge.net/projects/fetchmail/files/branch_6.6/
Improve mail/fetchmailconf:
- Replace PORTVERSION with DISTVERSION.
- Fix antipattern "BUILD_DEPENDS=RUN_DEPENDS".
- Fix warnings from portclippy.
PR: 296204 283227
[4 lines not shown]
[COFF] Make ICF compare .pdata xdata references
ICF must not fold functions solely because their .text is identical when their unwind or EH information differs. On AMD64 and ARM64, .pdata records describe code ranges and point at the unwind data used for unwinding and EH dispatch, so different reachable .xdata gives otherwise identical functions different semantics.
Record live .pdata records by the code section they describe and compare those records during ICF, following .pdata relocations to compare referenced .xdata sections directly. This keeps folding valid when the reachable unwind data is equivalent, while preventing folds for object files where old MSVC compilers did not associate .xdata with the parent .text COMDAT.
Drop the post-ICF duplicate .pdata removal workaround, update the existing test expectations, and add an ARM64 variant covering the two-field .pdata form.
