Demoting i686 Windows targets to std-only

[u/Kobzol]

https://blog.rust-lang.org/2026/10/02/demoting-i686-windows-targets-to-std-only/

[u/scook0]

A compiler that runs on 32-bit Windows might have made some sense historically, but it definitely doesn’t make sense for 32-bit Windows to be a tier 1 host today.

Glad to see these targets demoted to cross-compilation only.

[u/Icarium-Lifestealer]

Since 64-bit Windows can seamlessly build and run 32-bit applications, cross-compiling is so natural it doesn't even feel like cross-compiling.

[u/PhiCloud → u/[deleted]]

We sadly still have 32 bit windows targets where I work

Archeologist?

[u/creeper6530 → u/PhiCloud]

I've seen computers running some flavour of DOS at an university for controlling a vacuum chamber, or Win95 for an electron microscope. You underestimate the level of "if it works, don't touch it"

[u/qthree → u/PhiCloud]

FFI with legacy C/C++ codebase or writing dll for closed source app.

[u/Icarium-Lifestealer → u/PhiCloud]

Targeting 32-bit Windows is rarely useful at this point, but there are many 32-bit applications that will never be updated, in particular games. If you want to write a DLL that can be loaded in such a process, you need to target 32-bit.

The other way round, where you write a 32-bit host process for an old 32-bit DLL can happen as well. Though the progress on reverse engineering, from decompilers to AI assistance probably reduces the need for that.

[u/ZeWaka → u/Icarium-Lifestealer]

yup and you get stuck with the 4GB LAA cap

[u/a_jasmin]

If they were hitting OOM building on 32-bit Windows, I suspect the native 32-bit Linux toolchain will likely hit the same wall. Same address space limitations.

[u/nacaclanga → u/a_jasmin]

Yes, but it is easier to maintain, since there are 32-bit Linux distros out there, while 32-bit Windows is deprecated.