[JITLink][COFF] Give external absolute symbols default scope (#239718)
Depends on #239712
Please review only the last commit of this set.
COFFLinkGraphBuilder makes every absolute symbol local, but ORC's
object interface lists an external one as a definition. So an object
with `.globl x` / `x = 5` fails to link with "Missing definitions".
Use the storage class, as lld-link does: external absolute symbols get
default scope. Static ones, such as @feat.00, stay local.
Assisted-by: Claude Code
---------
Co-authored-by: Lang Hames <lhames at gmail.com>
[Offload][Omp] Fix libomptarget OMPT disconnect segfault (#243190)
Libomp is calling libomptarget `finalizeLibrary` as part of its `atexit`
tear-down process. But because the order of library dependencies,
libomptarget deinitializes first so when `finalizeLibrary` is called,
calling even a simple `ODBG` (with debug enabled) results in a segfault
because the stream has already been destructed.
In this PR, we ensure that OMPT is disconnected (in libomptarget) at
deinit at the latest and avoid doing that again if recalled from libomp.
Also, the LibraryFinalizer was never used (and in any case it should be
called before olShutDown) so simplify the disconnect to the minimum.
[RelLookupTableConverter] Support table with poison elements (#244155)
Support lookup tables with poison holes. We can convert this to a
relative lookup table with poison elements.
py-zope.testrunner: updated to 8.4
8.4 (2026-11-19)
- Add support for Python 3.15.
- Drop support for Python 3.10.
- Fix running layers in a subprocess on Python 3.15 when started via
``python -m zope.testrunner``: our ``profiling`` module shadowed the new
stdlib ``profiling`` package.
haproxy: updated to 3.4.8
3.4.8
- DOC: configuration: document AWS-LC compatibility restrictions
- BUG/MEDIUM: stats-file: shm-stats-file be counters not working anymore
- MINOR: quic: use the listener for Retry and Version Negotiation emission
- MINOR: quic: define a function to emit a datagram on a listener socket
- BUG/MEDIUM: quic: use datagram destination as source for Retry
- BUG/MINOR: quic: use datagram destination as source for stateless reset
- BUG/MINOR: quic: use datagram destination as source for version negotiation
- REGTESTS: quic: check Retry source address on a wildcard listener
- BUG/MINOR: quic: handle EINTR on emission of packets without connection
- BUG/MINOR: mux_quic: prevent RS/SS on unistream with hq-interop
- BUG/MINOR: check: do not inspect errno if conn FDLESS
- BUG/MINOR: mux_quic: do not crash on SE_SHR_DRAIN shut
- BUG/MEDIUM: peers: keep the earliest sync task deadline
- DOC: config: explain per ACL line limitations
- BUG/MINOR: quic: valid NEW_TOKEN connections are counted as half-open
- BUG/MEDIUM: cli: Fix parsing of big payloads with dynamically allocated buffer
[137 lines not shown]
[Offload] Avoid shadowing of test variables in the unittest ASSERT macros (#243921)
ASSERT_SUCCESS, ASSERT_SUCCESS_OR_UNSUPPORTED, ASSERT_ERROR and
ASSERT_ANY_ERROR store the checked result in a local variable named Res.
This is a ticking bomb: Res is also the name the test code itself uses
for results, e.g. 'ol_result_t Res = olInit(nullptr)' in olInit.cpp and
Environment.cpp, and several helpers in Fixtures.hpp and Properties.hpp.
Passing such a variable to one of the macros, e.g. ASSERT_SUCCESS(Res),
expands to 'ol_result_t Res = Res'. The macro's local shadows the test's
variable, is initialized from itself and is then dereferenced, so the
test crashes instead of checking the result. It only works today because
nobody happened to pass a variable named Res to these macros yet.
Rename the macro local to Res_ so it unlikly to collide.
Assisted-by: Claude
[CGP] Vector LSR postcommit comments addressed (#240839)
Fixing up postcommit problems found in #226197
* Use CreatePtrAdd instead of CreateGEP
* Use TypeAllocSize of SourceElementType
* Add test for i24 indexing
[flang][OpenMP] Exclude user-defined reductions from assumed bounded recipe effects (#240814)
Currently, user-defined reduction recipes may have their memory effects
assumed to be bounded, for example through the presence of
a`task_reduction_assume_bounded_recipe_effects` attribute. However
user-defined reduction recipes may access storage beyond their operands,
violating the operation contracts of the
`*_reduction_assume_bounded_recipe_effects` attributes.
Add a new flag `hasUserDefinedReduction` tracking whether a construct
with a reduction has any user-defined reduction recipes.
I'm not aware of any other way of doing this, for example in the
existing `canAssumeBoundedRecipeEffects` helper functions a variable
symbol may be involved in multiple reductions.
AI-Assisted-by: Codex
[JITLink] Skip allocation for graphs with only empty sections (#239712)
An object whose only definitions are absolute symbols still has an
empty __text section on MachO. JITLinkerBase sent its graph to the
memory manager, and FinalizedAlloc asserted on the empty allocation.
Skip sections with no blocks, as BasicLayout does.
Assisted-by: Claude Code
Co-authored-by: Lang Hames <lhames at gmail.com>
[AMDGPU] Preserve noclobber after acquire operations from a different addrspace (#231855)
Follow-up to #219991 to address reviewer comments:
AMDGPUAnnotateUniformValues should annotate uniform global loads as
`!amdgpu.noclobber` if the memory they are reading is never clobbered (since
kernel launch) before the load is executed.
PR #219991 strengthened the logic to consider acquire operations before the
load as clobbering (because they cause stores from other threads to be observed
by the load without a data race).
This PR weakens this criterion to ignore acquire operations that don't affect
the global address space (because they don't affect what the load in question
may or may not see). This addresses the performance-relevant case of s_barriers
with LDS-only fences.
The logic is still overly pessimistic for one-as load acquires, they could also
be ignored when looking for clobbering operations.
Disclaimer: Claude gave review comments and suggestions that I addressed during
[4 lines not shown]
pluginctl: enforce primary mode as selected by caller
While here sort the mode cases and add a print_help() wrapper.
Reported by: @dmuensterer
(cherry picked from commit 84c6837c90e7dec510972860cc19ab08c12f7466)
configd: restrict service stop and similar actions to wheel,wwwonly (#11233)
Addition to https://github.com/opnsense/core/commit/676d307294fe22d84b73f9639559702872b554bf
which restricted each service's own stop, the state kill actions,
clearing logs and disconnecting IPsec sessions. Still open:
- service stop
- filter flush states, filter flush sources
- system flush config_history
- ids drop alertlog
- openvpn kill
- captiveportal disconnect
None has a description, so none can be scheduled, and their only
callers in core are the web GUI and the API.
(cherry picked from commit dba1fac31a5ceae325f8e5a8ffb13366893728b0)
[LI] Test shrinkSubRangeToUses handling of early-clobber uses
An instruction could potentially read a subrange that also gets
redefined at the early-clobber slot. The test explicitely uses an
instruction with no register ties.
This makes the test a bit weird, because LLVM is supposed to guarantee
that the early-clobber register won't be used by any other input (unless
it's tied to the def).
See https://llvm.org/docs/LangRef.html#output-constraints
[PowerPC] Make `isa-v207-instructions` imply `isa-v206-instructions` (#233704)
Most `FeatureISA*` features imply former versions, with the exception of
`FeatureISA2_07` to `FeatureISA2_06`. There isn't a reason for this
because 2.07 should be backward compatible with 2.06 ([hwcap] sets 2.06
for all future ISA versions), and it wouldn't make sense to disable 2.06
instructions if 2.07 is enabled. Thus, make the impliciation explicit.
Note that this is effectively non-functional since 2.06 is already
implied as part of `P7InheritableFeatures`, which are picked up by all
future ISA versions.
[hwcap]: https://docs.kernel.org/arch/powerpc/elf_hwcaps.html
[VPlan] Mask all in-loop reduction links with the blend's edge mask (#243899)
When an in-loop reduction chain reaches the exit value through a phi
(converted to a VPBlendRecipe), the blend was folded to its non-phi
operand and each link was masked only by its own block mask. Links that
execute on paths where the phi selects the reduction phi instead, e.g.
a link in the loop header with the phi in the latch, were reduced
unmasked.
The chain only contributes on the blend's edge from the chain, so mask
all links with the blend's mask for that operand and place the
reductions in the blend's block, where the mask is defined.
PR: https://github.com/llvm/llvm-project/pull/243899
[IndVarSimplify][SCEV][NFC] Add tests for LFTR losing the constant max trip count
When LFTR of IndVars rewrites a loop exit like i >s C
to i + 1 == smax(start, C + 1),
SCEV's constant max backedge-taken count of the loop gets worse.
Add tests showing it.
Assisted-By: Claude
[IndVarSimplify] Use context to prove a narrow IV def non-negative
When IndVars widens an IV, it checks for each narrow def
(the IV and values computed from it) whether it is
non-negative on every iteration.
If it is, zext and sext of it are equal. Then when IndVars
idens the def's users, they can choose to use either
the sext or zext of the def.
Previously, we didn't use context to prove the non-negativity of def.
Now ask SCEV about the def non-negativity at its context -
the def instruction itself.
This allows SCEV to infer facts from the dominating guards and assumes.
This in turn allows eliminating unnecessary truncs/zexts. E.g. in
if (m > 0)
[9 lines not shown]
[IndVarSimplify][NFC] Add a negative test for zext elimination
Add a test for a zext of an nsw add of a sign-extended IV, where the
add may be negative.
Also rewrite a stale comment of an existing test.
Assisted-By: Claude
[LoopVectorize][NFC] Add tests for runtime checks with a widened IV index
In
if (start <u len && start - 32 <u len) // len >=s 0
for (int32_t i = start; i < n; i++) a[i] = a[i - 32];
i - 32 >=s 0, so the distance between a[i] and a[i - 32] is always 32.
If the loop has an i64 IV and i - 32 is computed in i64, it is
vectorized without runtime checks.
If i - 32 is computed in i32 and zero-extended, the vectorizer
emits an overflow check and an alias check.
Add tests for both forms.
Assisted-By: Claude
dpkg: updated to 1.23.12
dpkg (1.23.12) unstable; urgency=medium
[ Guillem Jover ]
* dpkg-source: Handle --help and --version as commands.
* dpkg-source: Add support for --robot for --version output.
* dpkg: Add minimal database structure audit support.
* dpkg: Add support for auditing the database contents.
* dpkg: Deprecate ancient alias for --selected-only.
* dpkg: Parse the --*-avail arguments before initializing the database.
* dpkg-name: Honor --overwrite with --symlink.
* dpkg: Use "installed" instead of "old" for maintscript error with no "new".
* dpkg-buildpackage: Fix --sign-pause long option name.
Thanks to Cheng Li <shiptux at gmail.com>.
* dpkg-buildpackage: Accept --sign-command auto and none arguments.
Reported by Cheng Li <shiptux at gmail.com>.
* dpkg-deb: Check for directory traversal symlinks in control.tar deb member.
Reported by Thai Duong <thai at calif.io>.
[70 lines not shown]
[SPIR-V] Type the capture_event_profiling_info value pointer as i8 (#230548)
The SPIR-V spec requires Value of OpCaptureEventProfilingInfo to point
to an 8-bit integer, but its pointee was inferred from other uses
Discussed in https://github.com/llvm/llvm-project/pull/229023
[AMDGPU] Describe MFMAs with a variant in MAIInstInfoTable (NFC)
- Add an MFMAVariant enum. Each MFMA pseudo gets its variant from
MAIInstInfoTable, a TableGen GenericTable.
- Look up an MFMA's co-execution info by its variant, as gfx1250 does
for WMMA, instead of matching every opcode.
- Give MFMAs without a co-execution model an empty window instead of
one that allows everything for 9 cycles, and have the hazard
recognizer start no window for them. The schedule does not change.
- Replace the is_dgemm and is_gfx940_xdl fields with the variant.
- Real MFMA opcodes get no variant, since nothing needs one.
- Strictly speaking this is not NFC, but no code path asks for the
co-execution info of a real opcode.
Assisted-by: Claude Opus 5.5