Rust Demotes 32-bit Windows Targets i686-pc-windows-msvc and i686-pc-windows-gnu to Std-Only Starting With Rust 1.100
Starting with Rust 1.100.0, the compiler team will stop shipping host tools for two 32-bit Windows targets, leaving only the standard library and requiring cross-compilation.
Overview
The Rust project will stop distributing the compiler for 32-bit Windows hosts. According to the Rust Blog, “With Rust 1.100.0, the following changes to 32-bit Windows targets will happen:” the i686-pc-windows-msvc target moves from Tier 1 with host tools to Tier 1 without host tools, and i686-pc-windows-gnu moves from Tier 2 with host tools to Tier 2 without host tools. The post, dated October 2, 2026, is credited to Mateusz Mikuła and Ralf Jung on behalf of the Compiler team.
What Changes
The Rust Blog says builds of the standard library will continue to be distributed, but “host tools such as the compiler will be no longer available.” The post adds that i686-pc-windows-msvc as a Tier 1 target still undergoes CI testing.
For developers, the practical consequence is spelled out in the same post: after Rust 1.100, it will no longer be possible to install toolchains on 32-bit Windows hosts. Building 32-bit Windows binaries will require cross-compiling from a still-supported host toolchain, such as a 64-bit Windows one. The post states that other 32-bit platforms are not impacted by this change.
The demotions were handled through two separate processes. The post points to RFC 3999 for the i686-pc-windows-msvc demotion and to MCP 1020 for the i686-pc-windows-gnu demotion. The RFC pull request is titled “Change i686-pc-windows-msvc from Tier 1 with host tools => Tier 1 without host tools” and is shown as merged.
Stated Reasons
The compiler team gives the age of the hardware and build problems as its rationale. The Rust Blog says 32-bit-only x86 desktop and server CPUs have not been sold for over 15 years and that general 32-bit Windows support ended in October 2025. It also reports that the team has “encountered compiler binaries crashing when built with the i686 MSVC target, and the GNU C++ toolchain failing with OOMs during LLVM build.”
The RFC text adds usage and technical arguments. It reports download counts extracted from Datadog metrics: i686-pc-windows-msvc had 432k downloads of the rustc host toolchain against 6.75M for std, while x86_64-pc-windows-msvc had 34.33M and 20.85M respectively. For i686-pc-windows-gnu, the RFC lists 72k toolchain downloads and 3.57M for std. The RFC concludes that the MSVC target’s std “receives far more downloads than its toolchain, because it is primarily used by cross-compiling.”
The RFC text also argues that a 32-bit host is poorly suited to running the compiler: “When builds wish to use more advanced features such as link-time optimization, the requirements can often exceed 4GiB.” It further notes that the 32-bit x86 host toolchains are tested by executing them on a 64-bit host rather than under a 32-bit kernel.
What We Don’t Know
- The sources reviewed do not give a release date for Rust 1.100. The previous stable release, Rust 1.99, is covered in an earlier Machine Herald report.
- The Rust Blog post says that “For the time being, the prebuilt standard library is still available,” so the long-term status of the
std-only targets is not stated.