[flang] Do not convert load and store FIR ops to memref if volatile (#212884)
Memref dialect has no way to express volatility currently. Let such FIR
operations to stay as FIR to be handled by CodeGen in path to LLVM.
clang: Emit "float-abi" module flag (#212985)
Emit the new module flag if it differs from the triple's
default.
Co-authored-by: Claude (Claude-Opus-4.8) <noreply at anthropic.com>
lang/gawk: update GNU awk to version 5.4.1
- Move options block below the common knobs
- Install some standard documentation files
Reported by: portscout
[SSAF] Close unsafe-buffer reachability over override families
An unsafe pointer reaching one override's parameter is equally unsafe in every
sibling and base override of that method, because the call site picks the
target dynamically. Without closing over the families, reachability depended
on which override the extractor happened to see the flow through, so a fix
suggested for the base could be contradicted by a derived override.
Mirroring is level-preserving: families relate slot entities, so a reachable
EPL propagates only to the same pointer level on its family members.
The closure runs after the pointer-flow DFS has converged and does not feed
its own output back in, so a flow edge out of a newly discovered EPL is still
missed. FamilyClosureDoesNotRerunDFS pins that gap.
§4 of rdar://179151603
[SSAF] Serialize virtual method summaries and families
Per-TU summaries and whole-program results cross process boundaries, and the
JSON layer refuses to write a summary kind it has no format for. Register both
sides so --ssaf-extract-summaries=VirtualMethod becomes usable and the family
result survives a round trip.
Deserialization tolerates a missing override list, since a root virtual method
legitimately has none.
§3 of rdar://179151603
[SSAF] Group virtual method slots into override families
A virtual call site can dispatch to any override, so the parameter and return
slots that occupy the same vtable slot across an override chain are
indistinguishable to a caller. Whole-program consumers therefore have to treat
them as one unit or they will reason about a slot that a call never actually
reaches.
Compute those units up front, keyed per slot, so consumers only need a map
lookup rather than their own traversal of the override relation. Overloads
occupy distinct vtable slots and stay in distinct families.
The family representative is the smallest EntityId in the class, which keeps
the result stable across runs.
§2 of rdar://179151603
[SSAF] Extract the virtual method override relation per TU
A virtual call may dispatch to any override of its callee, so a whole-program
analysis cannot reason about a method's parameters and return value in
isolation. It needs to know which method overrides which, and which slots
that relates. Collect this per TU, so a later pass can join the related
slots into families.
JSON serialization lands separately, so the summary is not writable via
--ssaf-extract-summaries yet.
§1 of rdar://179151603
net-mgmt/netbox: Update to 4.6.6
Changelog:
Enhancements:
* Enable the selection of VLANs scoped to a device's cluster or cluster
group when assigning VLANs to interfaces
* Render colored badges for custom field choices in tables
* Change the default color of the DHCP IP address status from green to
purple to distinguish it from "available"
* Introduce an "any" lookup for the tag and tag_id filters to match
objects assigned any of the specified tags
* Add a header_safe Jinja2 filter for sanitizing HTTP header values
Performance Improvements:
* Improve the speed of bulk object deletion by avoiding per-object
cascade handling and N+1 counter updates
* Avoid an unnecessary queryset evaluation when rendering export
templates
[54 lines not shown]
net-mgmt/netbox: Fix build after 3496c09fda1b
* Switch to the recently created py-social-auth-core4 port, because
NetBox is not compatible with newer versions of py-social-auth-core
due to several breaking changes.
* Bump PORTREVISION due dependency change.
PR: 297152
(cherry picked from commit fd3868f3a8b61ae2b3c273f6c4f2abd4d62dc0f1)
www/py-dj60-social-auth-app-django: Fix build after 3496c09fda1b
* Although there are already newer releases that are compatible with
py-social-auth-core >= 5, they also introduce quite a few breaking
changes along with py-social-auth-core 4.9.0+, so updating the port
is not an option at this time.
Therefore, switch to the recently created py-social-auth-core4 port
for now to fix the fallout and avoid regressions.
* Bump PORTREVISION due dependency change.
PR: 297152
Reported by: Einar Bjarni Halldórsson, pkg-fallout
(cherry picked from commit b91684dd1db4e8edf37382462d55601c2a0a5374)
security/py-social-auth-core4: New port
This is the core component of the python-social-auth ecosystem, it
implements the common interface to define new authentication backends
to third parties services, implement integrations with web frameworks
and storage solutions.
PR: 297152
(cherry picked from commit f30b3052c7cd4f71ec433ee4e037b1b78ba75266)
[VPlan] Use subpattern-m_VPValue in simplifyRecipe (NFC) (#213268)
Use the subpattern variant of m_VPValue introduced in 8db13de ([VPlan]
Remove redundant x && (y && x) -> x && y combine, #213219) to improve
code in simplifyRecipe.
[RISCV] Fix incorrect lowering of VECTOR_INTERLEAVE on fixed vectors (#212642)
This is the sibling patch of #207254, as it turns out VECTOR_INTERLEAVE
has the same problem on fixed vectors as well.
Instead of converting individual operands into scalable vectors, this
patch puts each of the operands directly onto stack using the fixed
vector version of segmented store intrinsics, before loading them back.
---------
Co-authored-by: Luke Lau <luke at igalia.com>
Reduce dp_lock scope for MOS writes
dp_mos_*_delta fields have no relation to other things protected
by dp_lock. Plus as write-mostly/read-once they are perfect
candidates for wmsums. Their conversion into such significantly
reduces dp_lock contention when writing lots of DDT/BRT blocks.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Signed-off-by: Alexander Motin <alexander.motin at TrueNAS.com>
Closes #18858
[libc] Fix math failures for fmod on NVPTX (#213168)
Summary:
Fixes some failing tests. Fmod's builtin has improper handling in the
NVPTX instruction so we should just use the generic version for now. The
Float128 implementation seems to have had some undefined behavior for
out of range behavior that only showed up now. Hopefully someone can
tell me if this is fixed correctly.
[CIR] Accept _BitInt up to 128 bits in x86_64 callconv lowering (#212668)
The x86_64 bridge in `CallConvLoweringPass.cpp` rejected every
`_BitInt`, so a function taking or returning one reported NYI even
though the ABI library already classifies these types. The classifier
has to be told the integer is bit-precise, and `mapCIRType` was dropping
that flag, which its two-eightbyte handling keys on. With the flag
forwarded, accepting widths up to 128 is mostly a matter of letting the
classifier's answer through. Wider widths stay rejected, for the reason
on the accept check.
Relaxing that check alone was not enough. `convertABIArgInfo` discarded
the classifier's coerce for every non-aggregate, which would have left a
`_BitInt(33)` as i33 where classic CodeGen passes i64. It now takes the
coercion path for a multi-register tuple coerce and for one wider than
the natural type. A narrower or equal coerce still means unchanged,
which is what preserves a `_BitInt(128)`'s 8-byte alignment.
Two `noundef` gaps against classic CodeGen remain. Neither mechanism is
[3 lines not shown]
[HashRecognize] Prevent values other than `ComputedValue` from exiting loop (#213080)
A check exists to prevent recurrences from having stray uses, but this
is only applied when a simple recurrence exists, and does not apply to
other values such as the induction variable. Since the loop is in LCSSA
form, check the incoming value from the loop on each of the exit block
PHIs and bail if any of them are not `ComputedValue`.
This replaces the existing check requiring `ComputedValue` to be used in
the exit block. Note that this no longer covers the case where the exit
block has no PHIs, and therefore does not use `ComputedValue`. In this
case, the loop is dead and will be cleaned up by DCE anyway.
AMDGPU: Add missing mqsad-insts to gfx13 frontend feature map (#213292)
fillAMDGCNFeatureMap omitted mqsad-insts for gfx1310/gfx13-generic, so
clang wrongly rejected __builtin_amdgcn_mqsad_u32_u8 on those targets
even though the backend enables the feature. Add it to the gfx13 case.
Co-authored-by: Claude (Claude-Opus-4.8)
