miniblog.

← Back to all posts
Nov 5, 2020 at 02:46
Fun compiler bug exposing an issue with LLVM (alias analysis): https://github.com/rust-lang/rust/issues/54878 Impressively, they are able to replicate the issue in C with clang, and even find a similar bug in gcc!
Enable noalias annotations · Issue #54878 · rust-lang/rust
Enable noalias annotations · Issue #54878 · rust-lang/rust
This issue tracks the undoing of the -Zmutable-noalias=no default introduced in #54639 on account of a bug in LLVM. cc @nagisa (Deja vu?)

Related Posts

Jan 23, 2026 at 00:09
1
Futhark's design is deliberately trying to stay simple to keep long term design sustainable. The author also has an interesting discussion of relative versus absolute paths in import syntax, and how relative paths can make local analysis easier.
Designing a Programming Language for the Desert
A high-performance and high-level purely functional data-parallel array programming language that can execute on the GPU and CPU.
Jan 15, 2026 at 00:07
LLMs are great at style transfer, and this works surprisingly well for syntactic transformations too. I rewrote a small website's EJS templates to 1500 LOC of TSX with a oneshot in Claude. It took ~12 minutes, but it just worked. (TSX seems nicer than EJS for static analysis.)
Jan 1, 2026 at 01:33
22
Is there a good canonical name for autofixes, where a static analysis tool can apply a change to resolve an issue? Clang calls them fix-its, LSP calls them quickfixes.