sqlite: match the extension entry point signature
Use the signature sqlite expects. sqlite3ext.h, which declares the
type, cannot be included here because it redefines the whole sqlite3
API to go through the loadable extension thunk, so declare the
structure the way it does.
[NFC][BOLT][AArch64] Simplify isWithinClusterRange parameters (#236980)
This is leftover from #228069 where we removed thunk estimation.
After that, isWithinClusterRange lambda no longer needs to know
how many clusters exist between Source and Target.
lang/babashka: Update to 1.13.229
Changes since 1.13.226:
1.13.229 (2026-10-27)
* Bump org.babashka/cli to 0.12.92
* Bump org.flatland/ordered to 1.16.13
* The bb resolver retries HTTP 429, HTTP 503 and dropped
connections, configured by the
aether.connector.http.retryHandler.* system properties
* The bb resolver no longer fails a version range on Windows when
two threads fetch one maven-metadata.xml at once
1.13.228 (2026-10-25)
* Block the keys of the compromised eMudhra intermediates, so
re-encoded certificates are rejected too
* The bb resolver sends proxy credentials on HTTPS CONNECT tunnels
[41 lines not shown]
audio/din: Update to 66.2
Changes since 65:
DIN Is Noise 66:
/*
new overtone tuning
the ratios of all intervals are octave shifted harmonics
of the key note.
now the default tuning
*/
/*
on beater and voice-modualtion editors:
infinite beat labels
[53 lines not shown]
[GVN] Preserve provenance when forwarding `<1 x ptr>` (#235505)
GVN forwards a store or load to a load of a different type by going
through an integer. Between `ptr` and `<1 x ptr>`, the sizes match, but
only scalar pointers skipped the integer path. So the value went through
`ptrtoint` and `inttoptr`, which drops pointer provenance, instead of
going through a `bitcast`.
```llvm
store <1 x ptr> %v, ptr %p
%l = load ptr, ptr %p
```
```diff
-%1 = ptrtoint <1 x ptr> %v to <1 x i64>
-%2 = bitcast <1 x i64> %1 to i64
-%l = inttoptr i64 %2 to ptr
+%l = bitcast <1 x ptr> %v to ptr
```
[OpenMP][offload] Size the grid of cross-team reductions by their size (#234190)
Use the ReductionDataSize for sizing the grid of xteam reductions.
Classify a reduction with a ReductionDataSize of 32bytes and more as
"large". Otherwise, we call this reduction "scalar" or "small".
Xteam reductions differ from regular loops in that they have two phases:
the intra-team reduction and the inter-team reduction. The cost of the
latter increases with the number of blocks and the ReductionDataSize.
For small reductions, aim for 16 waves/CU. For large reductions, aim for
1 block/CU.
For Generic and Generic-SPMD loops, we only use this heuristic for large
reductions and use the regular gris size heuristic otherwise since there
is currently no data for these situations.
This is an upstream port of the corresponding downstream. Measurements
have been made on MI210, MI300A, MI300X, MI350X, and MI450.
Claude assisted with this patch.
be more careful when killing a ProxyCommand (including implicit ProxyJump
ones); observe if it already has exited via the main ssh.c SIGCHLD handler
and wrap the kill in sigprocmask() to avoid races.
Prevents SIGHUP from being delivered to an unrelated process if the proxy
command's PID is recycled.
Antropic ANT-2026-ODQD8QBH
Correctly error on a algorithm allowlist that removes all algorithms, e.g.
`PubkeyAcceptedAlgorithms -*` rather than defaulting back to the full list
Anthropic ANT-2026-O2RQ9GNA
set a glob(3) error callback when globbing Include files to allow
discrimination between missing files/directories and failure to open
a file or directory.
Avoids possible (though unlikely) situation where a local attacker could
cause an Include'd file from being processed by doing tricks like hitting
fd limits at the right time.
Anthropic ANT-2026-NF7CR4JX
[libc] Reset fatal signal handlers in death test subprocesses (#236679)
Death tests (EXPECT_DEATH/ASSERT_DEATH) run the callback in a forked
child and check that the child was killed by a signal. If the test runs
under a runtime that installs its own handlers for fatal signals, the
child may not die from the signal at all. For example, on x86-64, ASan
with `handle_sigill=1` catches the SIGILL raised by `__builtin_trap()`,
prints an error report and calls `_exit()` (with the default
`abort_on_error=0` on Linux), so the test fails with:
Expected [] { optional<int> opt_empty; (void)opt_empty.value(); } to be
killed by a signal
But it exited normally!
This is what happens to the death tests in optional_test and
expected_test, as well as the null-check death tests, when run with
`ASAN_OPTIONS=handle_sigill=1`. ASan handles SIGSEGV, SIGBUS and SIGFPE
by default, so tests expecting those fail even with default options.
That's why pkey_test and the libgen death tests are not built under
[30 lines not shown]
