www/py-django-bootstrap3: Unbreak build after 21c2f9c595ac
* Relax the version requirements for py-uv-build which has been updated
recently.
Reported by: pkg-fallout
games/anki: Extend memory usage of NodeJS during build
* Set a higher value for V8's old memory to fix OOM issues during build:
[...]
vite v6.3.6 building for production...
transforming...
<--- Last few GCs --->
[85302:0x40cbfe36a000] 61573 ms: Mark-Compact (reduce) 505.7 (525.0) -> 502.2 (512.8) MB, pooled: 0 MB, 53.70 / 0.00 ms (+ 530.4 ms in 111 steps since start of marking, biggest step 5.2 ms, walltime since start of marking 659 ms) (average mu = 0.194, [85302:0x40cbfe36a000] 62211 ms: Mark-Compact 503.3 (512.8) -> 498.8 (515.5) MB, pooled: 0 MB, 631.85 / 0.00 ms (average mu = 0.113, current mu = 0.009) allocation failure; scavenge might not succeed
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0x19a5b74 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/local/bin/node]
2: 0x1be1c44 node::inspector::protocol::IO::DomainDispatcherImpl::~DomainDispatcherImpl() [/usr/local/bin/node]
3: 0x1e1a6b0 v8::internal::HeapLayout::CheckYoungGenerationConsistency(v8::internal::MemoryChunk const*) [/usr/local/bin/node]
4: 0x1e1d5f4 v8::internal::HeapLayout::CheckYoungGenerationConsistency(v8::internal::MemoryChunk const*) [/usr/local/bin/node]
[5 lines not shown]
AMDGPU: Set transient stack alignment to 4
Some of the frame index handling code seems to assume
it can preserve values in SCC through an add by using an
add carry, and clearing the low bit of the resultant pointer,
which means an odd SP value could be corrupted. I haven't
found a case where this was meaningful; we always end up
using a 4 byte aligned pointer anyway. Set this just in case.
[mlir] targeted verification for transform "inlining" (#192956)
When merging named transform sequences into their include locations,
rely on the InlinerDialectInterface implementation newly added to the
transform dialect instead of the full verification after the fact. This
enables us to only verify aspects of the IR that may change in a way
compatible with the rest of the infra, reducing the overall cost of the
process.
Use `LogicalResult` as appropriate instead of returning dummy
`InFlightDiagnostic` while I'm here.
Assisted-by: Claude Opus 4.7 / Cursor
[lldb] Remove unused ExpressionPathOptions: NoFragileObjcIvar, NoSyntheticArrayRange (NFC) (#193336)
As of #193120, `eExpressionPathOptionsNoFragileObjcIvar` and
`eExpressionPathOptionsNoSyntheticArrayRange` are no longer used
anywhere, and aren't expected to be used again.
[flang][OpenMP] Remove unused member, NFC (#193512)
After e8e8b6a3d8616b5d6572f9e16442cc97ef3867bd, the member
`privateDataSharingAttributeObjects_` of OmpAttributeVisitor is no
longer used. Remove it and the associated accessor functions.
[flang] Update LIT test for big-endian platform (NFC) (#193309)
Specify the kind type parameter to ensure the 64-bit value is correctly represented
in the big endian environment.
[libc] Add struct sockaddr_storage (on linux) (#192978)
This deceptively simple patch has one catch. The POSIX standard states:
"""
When a pointer to a sockaddr_storage structure is converted to a pointer
to a sockaddr structure, or vice versa, the ss_family member of the
sockaddr_storage structure shall map onto the sa_family member of the
sockaddr structure. When a pointer to a sockaddr_storage structure is
converted to a pointer to a protocol-specific address structure, or vice
versa, the ss_family member shall map onto a member of that structure
that is of type sa_family_t that identifies the protocol's address
family. When a pointer to a sockaddr structure is converted to a pointer
to a protocol-specific address structure, or vice versa, the sa_family
member shall map onto a member of that structure that is of type
sa_family_t that identifies the protocol's address family. Additionally,
the structures shall be defined in such a way that the compiler treats
an access to the stored value of the sa_family_t member of any of these
structures, via an lvalue expression whose type involves any other one
[20 lines not shown]
NAS-140717 / 26.0.0-BETA.2 / Move VM NVRAM and TPM atomically with VM rename (by Qubad786) (#18775)
## Problem
Two bugs in the VM lifecycle leave on-disk state out of sync with the VM
record:
1. **Rename loses TPM state and can desync the DB.** `do_update` only
renamed the NVRAM file; the TPM state directory
(`/var/db/system/vm/tpm/{id}_{name}_tpm_state/`) was never touched.
After rename, pylibvirt generates XML pointing libvirt/swtpm at the new
name, the old-named TPM dir is orphaned, and swtpm silently initialises
fresh empty state — Windows 11's TPM appears reset, BitLocker keys and
measured-boot state are lost. On top of that, the DB update ran *before*
the filesystem rename, so any I/O failure left the DB at the new name
while the files stayed at the old one. The `CallError` raised on a
missing NVRAM was also misleading — libvirt recreates NVRAM from its
`template=` attribute on first start.
[43 lines not shown]
[flang][OpenMP] Remove unused member, NFC
After e8e8b6a3d8616b5d6572f9e16442cc97ef3867bd, the member
`privateDataSharingAttributeObjects_` of OmpAttrVisitor is no longer
used. Remove it and the associated accessor functions.
[RISCV] Functional llvm.vector.reduce.mul on scalable types (#193094)
RVV does not have an instruction for performing a horizontal multiply
reduction (either integer or floating point). However, a user of clang
can explicitly write at least the integer form via the
__builtin_reduce_mul construct, and currently we just crash when
compiling this.
This change converts the crash into functionally correct scalar loop to
process each element one by one at runtime. This will be slow, but at
least correct.
Note that to my knowledge we can't generate the floating point one
directly from C, but I decided to handle both for completeness while I
was here.
Written by Claude Code with guidance and review by me.
[lldb] Remove trailing newlines from AppendErrorWithFormat calls (part 2) (#193168)
Follow up to #192965.
This call adds a newline if there isn't one. Changing these will
eventually let us always add a newline, which is in line with
the other methods on CommandReturnObject.
This is a small part of calls found with:
* VSCode search for
`(\.AppendErrorWithFormat\(([\s\r\n]+)?"(?:(?:\\.|[^"\\])*))\\n"` and
replace with `$1"`.
* Asserting that the last character of the format string is not a
newline.
* Manual inspection.
arm: fix float to integer conversion with `+mve` (#193319)
Fix an instruction selection failure when using the `+mve` (and an implied `-mve.fp`)
target feature. From what I understand, e.g. based on
https://reviews.llvm.org/D60694, this combination of target features
enables float registers and loads/moves, but no real FP operations.
Hence
https://godbolt.org/z/xeTcbqMqx
```llvm
define i32 @foo(float %x) {
%i = call i32 @llvm.fptosi.sat.i32.f32(float %x)
ret i32 %i
}
```
compiled with `llc -mtriple=thumbv8m.main-none-eabi
-mattr=+v8.1m.main,-mve.fp,+mve -O2` hit
[8 lines not shown]
[LoopInterchange] Fix out-of-bounds accesses in tests (NFC) (#193272)
These tests trigger out-of-bounds accesses. Fix them by decreasing the
backedge-taken counts of the loops, and add pseudo code.
