[DWARFLinker] Add missing DebugInfoDWARFLowLevel dependency (#229222)
Since afca127bbb62, hasImplicitAddressLocation() in LLVMDWARFLinker uses
DWARFExpression from DebugInfoDWARFLowLevel. Builds with
BUILD_SHARED_LIBS=ON failed to link libLLVMDWARFLinker with undefined
references to DWARFExpression. Add the component to the CMake library,
and the matching dependency to the GN build.
Assisted-by: Claude
DAG: Fix error message casing to match style policy (#229212)
The developer guidelines suggests that diagnostic messages should start
with a lowercase letter and not end in a period
Co-authored-by: Claude <noreply at anthropic.com>
[AArch64][Win] Account for the fixed object area when classifying CSR (#222111)
In Windows frames, the fixed object area sits above the callee-saved
register area:
+---------------+
| Fixed objects |
+---------------+
| Callee-saved |
+---------------+
| Locals |
+---------------+
Include the fixed object area in the callee-saved threshold used by
`resolveFrameOffsetReference()`. Without this, objects in the
callee-saved area can be incorrectly addressed through the base
pointer in stack-realigned frames.
This became visible after #147421 moved catch objects into the fixed
[3 lines not shown]
[MLGO] Make regalloc eviction input tensor shapes runtime variables (#224598)
The column count was hardcoded to 33 for X86
It now comes from `-mlregalloc-num-allocatable-regs` (default 32, plus
one column for the candidate), compiled model whose shapes do not match
falls back to the default policy
[lldb] Use file(MAKE_DIRECTORY) to create header staging dir (#228606)
This simplifies the build graph for modifying lldb headers for
installation. It also fixes the `clean` target by not making a target
responsible for creating this directory. CMake will create it as needed
during configuration time instead of at build time.
rdar://161109746
[SPIR-V] Mark elementwise intrinsics IntrTriviallyScalarizable (#227286)
This mirrors the DirectX intrinsics
The SPIR-V legalizer will use it to split elementwise intrinsics with
illegal vector widths
Required for https://github.com/llvm/llvm-project/pull/227287
security/snort: Use libpcap from ports
Summary:
Add explicit lib version to force port to use libpcap from ports and
avoid it rebuilding every time base packages are upgraded
Sponsored by: Rubicon Communications, LLC ("Netgate")
Reviewed By: dvl
Differential Revision: https://reviews.freebsd.org/D60381
security/snort3: Use libpcap from ports
Summary:
Add explicit lib version to force port to use libpcap from ports and
avoid it rebuilding every time base packages are upgraded
Sponsored by: Rubicon Communications, LLC ("Netgate")
Reviewed By: bofh
Differential Revision: https://reviews.freebsd.org/D60383
net/libdaq: Use libpcap from ports
Add explicit lib version to force port to use libpcap from ports and
avoid it rebuilding every time base packages are upgraded
Sponsored by: Rubicon Communications, LLC ("Netgate")
Reviewed By: bofh
Differential Revision: https://reviews.freebsd.org/D60383
[mlir][OpenACC] Skip implicit routine marking for host-only calls (#227758)
Calls nested in a host-only branch of `acc.on_device` do not run on the
device. Do not try to attach implicit acc routine information to them.
[CI] Exclude CIR from Windows premerge testing (#229208)
After #227957, the check-clang-cir target is only defined when
CLANG_ENABLE_CIR is ON. The Windows premerge build never sets that
option (only monolithic-linux.sh receives enable_cir), but
compute_projects.py still selects check-clang-cir for CIR changes on
Windows. Every PR touching CIR now fails the Windows job before any test
runs:
ninja: error: unknown target 'check-clang-cir'
Before #227957 the target existed unconditionally, and the CIR tests
were all unsupported on Windows because CIR was disabled, so excluding
CIR there loses no coverage. It also stops building mlir for CIR-only
changes on Windows.
Enabling real CIR testing on Windows (passing enable_cir through to
monolithic-windows.sh) can be done separately.
[2 lines not shown]
security/vuxml: Fix entry for expat2 CVE-2026-93990
expat2 package is using expat as package name
PR: 299162
Reported by: Tomáš Čiernik <tomas at ciernik.sk>
[DWARFLinker] Relocate DW_OP_addrx by the delta of its own symbol (#228583)
When rewriting DW_OP_addrx or DW_OP_constx into a relocated address,
DWARFLinker applied the adjustment of whatever owned the expression.
For a location list that is the enclosing function, but the .debug_addr
entry may name a data symbol, which the linker moves by a different
amount. For a variable holding the address of _g at 0x100004008 this
produced:
[0x100000418, 0x100000424): DW_OP_addr 0x100000790, DW_OP_stack_value
Look up the relocation of each operand's own .debug_addr slot instead,
the way a variable's single location is already handled, and fall back
to the owner's adjustment only where there is none. Do this in both the
classic and the parallel linker.
rdar://188852150
Assisted-by: Claude
www/evcc: update to 0.316.2
Switch back to vite for building till vite-plus got full native
FreeBSD support (vite-plus tries to download linux binaries).
Switched back to node24, node26 core-dumps while executing npm.
Add braces to multi-line if in asm parser
Change-Id: I20476ccf51eb2901a1181aa038d15e6c1e99e8cc
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply at anthropic.com>
pipe(2): Restore kevent EVFILT_READ/WRITE success on wrong pipe end.
Missed a spot when gathering the hunks in the previous change for
this.
PR kern/60851: change in pipe kevent EVFILT_READ/WRITE on wrong end
[VPlan] Handle div/rem replicate recipes outside regions in cost. (#229203)
VPReplicateRecipe::computeCost unconditionally dereferenced getRegion()
for div/rem recipes. A non-single-scalar replicate recipe may be hoisted
out of the loop region into the vector preheader, where getRegion()
returns nullptr, causing a crash. Treat recipes outside any region as
unpredicated, matching the existing handling for loads and stores.
Fixes https://github.com/llvm/llvm-project/issues/229124.
Revert "pipe(2): Add memory safety diagnostics."
This was rather sloppily done (from my local tree, not cleaned up
before committing in haste in an attempt to help diagnose the spate
of crashes that have been seen today). Will redo this a little more
tidily.
PR kern/59056: poll POLLHUP bugs
