Rust 1.97.1 fixes LLVM miscompilation, urges stable users to update

Rust 1.97.1 landed on July 16 as a patch release built around one job: fixing a miscompilation in an LLVM optimization before it spread further into stable builds. The Rust team backported an LLVM submodule bump that carries the LLVM-side remedy, and it also reverted a rustc change that was known to trigger the bug.

That rustc revert was described as a precaution, not a strictly required part of the fix, which is exactly the kind of conservative move you want from a stable toolchain. The bug was serious enough to be tracked in rust-lang/rust issue #159035, titled segfault on Rust 1.97.0, so this was never just a cosmetic compiler quirk. If you are compiling production code on stable Rust, the direct path is `rustup update stable`.

The release fits Rust’s normal channel discipline. Stable builds go out every 6 weeks, with occasional point releases reserved for critical bug fixes or security patches, and 1.97.1 falls squarely into that bucket. Pre-release testing for the patch was already lined up for July 16, and the release team pointed testers to the dev-static distribution index on July 14.

Community discussion around the 1.97.0 failure suggested the regression may have come from the jump from LLVM 19 to LLVM 20, and LLVM had already fixed the issue upstream. That made the Rust-side response relatively clean: pull in the upstream LLVM fix, then remove the rustc change that could trip the bug path. For teams pinning toolchains in CI, distro packagers, and anyone shipping binaries from the stable channel, the update matters because compiler miscompilations can silently change program behavior without touching a line of application code.

Rust 1.97.1 does not bring a flashy feature list, and that is the point. Stable users got a release focused on trust, not novelty, after a compiler-level bug showed how quickly a bad optimization can turn into a crash.