{
  "id": 13046152,
  "title": "Demoting i686 Windows targets to std-only",
  "url": "https://urgent.news/2026/10/08/demoting-i686-windows-targets-to-std-only",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-08T21:39:50.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://blog.rust-lang.org/2026/10/02/demoting-i686-windows-targets-to-std-only/"
  },
  "original_language": "en",
  "account": "Rust 1.100.0 introduces significant changes to 32-bit Windows targets. While standard library builds will continue, host tools like the compiler will no longer be available for these platforms. i686-pc-windows-msvc, a Tier 1 target, will still undergo CI testing. However, to build 32-bit Windows binaries, cross-compiling from a still-supported host toolchain, such as a 64-bit Windows one, will be necessary moving forward. The development platforms for these targets are increasingly obsolete, with x86 CPUs no longer being produced for over 15 years and 32-bit Windows support ending in October 2025. Building these targets on modern x86_64 hardware has proven problematic, with compiler binaries crashing and the GNU C++ toolchain failing due to memory issues. As a result, cross-compiling from a more supported platform has been deemed the best course of action. The prebuilt standard library will remain available, and i686-pc-windows-msvc will continue to be tested on CI after Rust 1.100. However, installing toolchains on 32-bit Windows hosts will become impossible after this update. Rust recommends cross-compiling from a supported host, like a 64-bit Windows toolchain, instead. The demotion of other 32-bit platforms is not affected by this change. For more details, refer to RFC 3999 for i686-pc-windows-msvc demotion and MCP 1020 for i686-pc-windows-gnu demotion.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}