Repository navigation
Tracking issue for release notes of #161681: Cross-compile i686-pc-windows-gnu std from x86_64 #161885
Description
This issue tracks the release notes text for #161681.
cc @mati865, @jieyouxu -- original issue/PR authors and assignees for drafting text
See the forge.rust-lang.org chapter about release notes for an overview of how the release team makes use of these tracking issues.
Release notes text
This section should be edited to specify the correct category(s) for the change, with succinct description(s) of what changed. Some things worth considering:
- Does this need an additional compat notes section?
- Was this a libs stabilization that should have additional headers to list new APIs under
Stabilized APIsandConst Stabilized APIs?
# Platform Support
- [`i686-pc-windows-gnu` is now a tier 2 without host tools target](https://github.com/rust-lang/rust/pull/161681)Tip
Use the previous releases for inspiration on how to write the release notes text and which categories to pick.
Release blog section
If this change is notable enough for inclusion in the blog post then this section should be edited to contain a draft for the blog post. Otherwise leave it empty.
Note
If a blog post section is required the release-blog-post label should be added (@rustbot label +release-blog-post) to this issue as otherwise it may be missed by the release team.
Activity
tgross35 commentedon Aug 31, 2026
Note that we had a blog post for the drop to tier 2 https://blog.rust-lang.org/2025/05/26/demoting-i686-pc-windows-gnu/, this may be worth the same since it changes the process needed for installing.
mati865 commentedon Aug 31, 2026
rust-lang/rfcs#3999 has been approved for 8 days already. So, maybe we should do one combined blog post?
Although msvc changes are technically more significant because that rfc drops host tools for tier 1 target.
tgross35 commentedon Aug 31, 2026
Oh yeah, that makes sense. This one just felt notable to me since you can no longer just install
nightly-i686-gnuit might be good to write up a workaround for testing. (I'm working on this currently, #general > Building for `i686-pc-windows-gnu` on GH actions)