[VectorCombine] Fix foldBitcastOfVPLoad reordering loads (#218336)
We were inserting the new vp.load where the bitcast was, which would
reorder loads. This should hopefully fix RISC-V buildbot failures that
were exposed after 93ac788df8ff
www/py-django-constance: Update 4.3.4 to 4.3.5
* Assume maintainership.
* Switch to the more preferred DISTVERSION.
Changelog:
https://github.com/jazzband/django-constance/releases/tag/4.3.5
PR: 297821
Reported by: Christos Longros
Co-authored-by: Kai Knoblich <kai at FreeBSD.org>
RISCV: Fix VectorPeephole null dereference on an undef vmerge true operand (#218328)
Also since this is an SSA pass, switch to using getVRegDef instead of
getUniqueVRegDef
Co-Authored-By: Claude <noreply at anthropic.com> (Claude Opus 4.8)
[mlir][vector] Verify multi_reduction reduction dimensions (#216854)
`vector.multi_reduction` does not bounds-check `reduction_dims`.
Out-of-range
entries verify cleanly and then crash the canonicalizer:
```mlir
%0 = vector.multi_reduction <add>, %a, %b [1, 2] : vector<1x4xf16> to vector<1xf16>
```
`getReductionMask()` builds `SmallVector<bool> res(sourceRank)` and
executes
`res[2] = true`. The `[1, -1]` variant indexes `res[(size_t)-1]`.
Reject out-of-range and duplicate dims in the verifier, following
`TransposeOp::verify`. The mask is reused by the shape-inference loop
below.
One existing test is itself the repro: `propagate-layout.mlir` uses `[1,
[10 lines not shown]
RISCV: Fix VLOptimizer null dereference on an undef slide amount (#218329)
Also since this is an SSA pass, switch from getUniqueVRegDef
to regular getVRegDef.
Co-Authored-By: Claude <noreply at anthropic.com> (Claude Opus 4.8)
tcp: cleanup whitespaces
Use tabs consistently in #defines
No functional change intended.
Reported by: Hannes Elfert
MFC after: 1 week
MFC to: stable/15
Reapply [Clang] Mark new as inaccessiblememonly if sane (#217652)
Reapply https://github.com/llvm/llvm-project/pull/197199 without changes
after https://github.com/llvm/llvm-project/pull/201375 improved our
errno TBAA reasoning.
-----
If `-fassume-sane-operator-new` (the default), assume that `operator
new` does not read or write accessible memory.
Currently, this assumption already exists due to special treatment in
BasicAA. I'd like to remove this special treatment (see
https://github.com/llvm/llvm-project/pull/197180), and instead rely only
on the `memory` attribute.
It's worth noting that this is consistent with GCC's interpretation of
the flag (where it is also enabled by default):
[5 lines not shown]
[lldb] Keep DW_OP_call_frame_cfa address-sized (#216684)
`DW_OP_call_frame_cfa` currently constructs a `Scalar` directly from
`lldb::addr_t`. Since `addr_t` is a 64-bit carrier, the result remains
64 bits
when evaluating an expression for a 32-bit target, and subsequent
address
arithmetic does not wrap at the target address width.
Normalize the CFA with the evaluator's existing `to_generic` helper
after it
is pushed. This preserves the existing frame lookup, error handling, and
`LoadAddress` value type while making the scalar use the target address
width.
Add an i386 unit test that verifies both 32-bit address arithmetic and
the
resulting `APSInt` bit width.
Fixes #210980
math/py-numpy-stl: upgrade to 4.0.0
Releases notes at https://github.com/wolph/numpy-stl/releases
Also:
- add category cad;
- change license to BSD 3 clauses;
- switch to pep517;
- remove cython and strip, and set NO_ARCH.
PR: 297446
Approved by: db (maintainer)
Fix AppVerifier GetThreadId(NULL) error in llvm::thread (#216941)
A recent change (64be34c562a23761dcb48a0a6a0b3ef0576c14c4) brought up a
behaviour change to the way llvm::thread checks if it is joinable. Prior
to the patch, a thread handle is checked if it's valid. The new
behaviour is to query a thread id and check if it's non-zero.
On Windows, the new behaviour means calling GetThreadId(handle) to
retrieve the thread id. This, however, results in errors when the thread
handle is not pointing to any active thread (NULL) and when running
applications under AppVerifier as it reports that a "system function is
called with a NULL handle". For applications using LLVM infrastructure
(in our case it is a MLIR-based compiler), the call stack looks like:
```
vrfcore!VerifierStopMessageEx+0x858
vfbasics!AVrfpHandleSanityChecks+0x3c
vfbasics!AVrfpNtQueryInformationThread+0x46
KERNELBASE!GetThreadId+0x33
my_app!llvm::llvm_thread_get_id_impl
[22 lines not shown]
[Mips] Use ELF binding when expanding PIC la (#217566)
A symbol already assigned to a section is not necessarily local. Use ELF
symbol binding when expanding PIC `la`, retaining the existing
section-based fallback for non-ELF targets, so defined default-visible
globals use the correct global GOT form.
Adds `llvm/test/MC/Mips/macro-la-pic-defined-global.s` covering global,
local, and `$25` call-register expansions.
Fixes #217371
www/code-server: Update to 4.133.0
Update to code-server 4.133.0, which bundles VS Code 1.133.0.
Changelog: https://github.com/coder/code-server/releases
Sponsored by: Netzkommune GmbH
[docs] Document `-mtriple` option in opt command guide (NFC) (#213942)
`-mtriple` option has been supported for a long time, but previously
lacked documentation.
pfsync: handle large MTU pfsync interfaces
pfsync packets were allocated with m_get2(), which can't return packets
larger than MJUMPAGESIZE. As a result 9k MTU pfsync interfaces simply didn't work.
Use m_get3(), which can allocate sufficiently large mbufs.
Extend the pfsync:bulk test case to provoke this problem.
PR: 297307
MFC after: 2 weeks
Sponsored by: Rubicon Communications, LLC ("Netgate")
(cherry picked from commit 7e2781fdcfdbe489cc07572d33dc36bca06a342d)
pfsync: handle large MTU pfsync interfaces
pfsync packets were allocated with m_get2(), which can't return packets
larger than MJUMPAGESIZE. As a result 9k MTU pfsync interfaces simply didn't work.
Use m_get3(), which can allocate sufficiently large mbufs.
Extend the pfsync:bulk test case to provoke this problem.
PR: 297307
MFC after: 2 weeks
Sponsored by: Rubicon Communications, LLC ("Netgate")
(cherry picked from commit 7e2781fdcfdbe489cc07572d33dc36bca06a342d)
[BasicAA][TLI] Treat local-linkage globals or known environments as not aliasing errno (#170290)
Errno cannot alias global variables with internal/private-linkage,
neither can it aliases globals on known environments, where errno is
known to be defined as a function call – unless targeting
freestanding/baremetal environments.
java/javamail: use the devel/javax-activation port for dependency
Simplifies the port a little.
Pet portclippy.
Approved by: ale
Differential Revision: https://reviews.freebsd.org/D59127
