Triple: Expose parseArch as a public method (#189648)
Clang has some code which is doing a direct arch name
string compare which should really be recognizing anything
usable as a triple architecture. It makes more sense to
directly parse the architecture than to construct a temporary
triple just to see what the parsed arch is.
For some reason the existing public parsing method is
getArchTypeForLLVMName. I'm not fully sure what the difference
between the 2 is supposed to be. My current guess is
getArchTypeForLLVMName is only supposed to handle the
canonical architecture name.
py-cairosvg: updated to 2.9.0
2.9.0
Version 2.9.0 released on 2026-03-13
WARNING: this is a security update.
Using a lot of recursively nested use tags could lead to long rendering times with relatively small inputs. CairoSVG now stops rendering when more than 100k use tags are rendered.
Using the --unsafe option allows to render larger documents.
Drop support of Python 3.9, add support of Python 3.14
ngtcp2: updated to 1.22.0
1.22.0
Consistent hex literals and integer suffixes
Add missing entries to .gitignore
Deprecate quictls
Introduce struct ngtcp2_stateless_reset_token
Fix assertion failure without get_new_connection_id
Migrate to new callbacks
Add ngtcp2_pkt_write_stateless_reset2
Add missing callbacks to callbacks test
Add ngtcp2_conn_get_active_dcid2 and ngtcp2_cid_token2
Prefer sizeof token instead of integer constant
Introduce struct ngtcp2_path_challenge_data
Store cid and token directly into frame
tests: Remove xcid_init in favor of make_xcid
tests: Inline initialization for transport parameters tests
tests: Make shared crypto objects static const
[59 lines not shown]
[Passes] Remove some optsize checks (#189369)
LibCallsShrinkWrapPass and PGOMemOPSizeOpt already check for optsize
attributes internally, so there is no need to handle this in the pass
pipeline.
The context here is that I'd like to make the pass pipeline completely
independent of Os/Oz so that we know for sure that function-level
optsize/minsize attributes behave identically to the pipeline-level
option.
py-async-lru: updated to 2.3.0
2.3.0
Added cache_contains() for read-only key lookup.
Changed cross-loop cache access to auto-reset and rebind to the current event loop.
Added AlruCacheLoopResetWarning when an auto-reset happens due to event loop change.
Forwarded cache_close(wait=...) for bound methods.
[AMDGPU][SIFoldOperands] Fix OR -1 fold
In SIFoldOperands, folding `or x, -1` to `v_mov_b32 -1` removed `Src1Idx`,
which is incorrect because `-1` is in `Src0Idx` (after canonicalization).
py-pygit2: updated to 1.19.2
1.19.2 (2026-03-29)
- Fix refcount and error handling issues in `filter_register(...)`
- Fix config with valueless keys
- New `Repository.load_filter_list(...)` and `FilterList`
- New `Odb.read_header(...)` and now `Odb.read(...)` returns `enums.ObjectType` instead of int
- Build and CI fixes
py-numpy: updated to 2.4.4
2.4.4
MAINT: Prepare 2.4.x for further development
BUG: Add test to reproduce problem
BUG: fix FNV-1a 64-bit selection by using NPY_SIZEOF_UINTP
BUG: avoid warning on ufunc with where=True and no output
DOC: document caveats of ndarray.resize on 3.14 and newer
TST: fix POWER VSX feature mapping
MAINT: numpy.i: Replace deprecated ``sprintf`` with ``snprintf``...
[Support][APint] Fix APInt::urem for edge case. Use `U.pVal[0] instead getZExtValue() (#189441)
Use `U.pVal[0]` instead of `getZExtValue()` in the
`APInt::urem(uint64_t)` power-of-two fast path. `getZExtValue()`
requires the entire APInt to fit into 64 bits, but this code can be
reached for multi-word values, which may trigger assertions
(`assert(getActiveBits() <= 64 && "Too many bits for uint64_t")`) or
otherwise mis-handle wide integers.
Also add simple test for edge cases.
Improvement for https://github.com/llvm/llvm-project/pull/189245
update to rspamd-4.0.0
this probably won't affect most users, but:
"Action required for per-user Bayes with Redis sharding: Jump Hash has
been replaced with Ring Hash (Ketama). Run rspamadm statistics_dump
migrate after upgrading or accept temporary accuracy loss as data is
re-learned. Single Redis server setups are not affected."
[ADT] implement countl_zero_constexpr and reuse it for countl_zero & bit_width_constexpr (#189111)
Implement constant evaluated `countl_zero_constexpr` similar to
`countr_zero_constexpr` and use it for `countl_zero` and
`bit_width_constexpr`.
Also, `countl_zero` now use fast intrinsic path for `uint8/uint16` types
(use `sizeof(T) <= 4` instead `sizeof(T) == 4`).
[CodeView] Expose fallible type accessors in TpiStream (#188299)
`LazyRandomTypeCollection` already has fallible functions for
`getType(TypeIndex)` this exposes them in `TpiStream` and does a mini
cleanup in `LazyRandomTypeCollection`'s `GetType`.
Context: #186948 saw a crash in LLDB where we call `GetType` without
checking the type index before calling the method. In `GetType` we
called `error(std::move(EC))`, which ignores the error in release mode.
The cause was the type index `0x80000169` in an `S_LOCAL`.
We now do a soft fail in release mode - we already check the error, so
we might as well return an empty value.
Aside: The type index there feels really unusual, the type indices in
other records around the `S_LOCAL` were in a similar range. Almost looks
like some integer over-/underflow.
