Two ARM64-specific compiler optimization bugs, in GCC 15/16 and Rust, hit curl
torutofu
51 points
7 comments
October 06, 2026
Related Discussions
Found 5 related stories in 96.5ms across 8,687 title embeddings via pgvector HNSW
- Scaling Memory Safety: AI-Assisted Rewrites of C/C++ Dependencies to Rust ndesaulniers · 12 pts · September 28, 2026 · 55% similar
- Scaling Memory Safety: AI-Assisted Rewrites of C/C++ Dependencies to Rust afdbcreid · 15 pts · August 24, 2026 · 55% similar
- How to speed up the Rust compiler in September 2026 trickypr · 242 pts · October 01, 2026 · 53% similar
- Bun 1.4 Rust rewrite is not looking good? tipiirai · 136 pts · August 19, 2026 · 52% similar
- Using GCC's Nested Functions with Wide Pointers and No Trampolines II uecker · 92 pts · August 15, 2026 · 52% similar
Discussion Highlights (3 comments)
edoceo
The social post links to this bug https://github.com/curl/curl/issues/23237
vlovich123
Not actually confirmed as compiler bugs yet. Here’s a similar bug where OpenSSL’s inline asm was wrong and probably only GCC was smart enough to try to exploit the bug: https://github.com/openssl/openssl/pull/23233 Same for rust - could be UB in quiche that is getting exposed.
rurban
Looks like a valid new optimization to me, which only fails on valgrind, which is a bit too strict with uninitialized values. In openssl's strlcpy. They'll deal with that.