3 ms·
https://forge.rust-lang.org/platform-support.html https://forge.rust-lang.org/platform-support.html is mostly accurate.
by steveklabnik 8y ago
https://forge.rust-lang.org/platform-support.html https://forge.rust-lang.org/platform-support.html is mostly accurate.
- robocat 8y agoWow: tier 1 contains no ARM or other CPU arch. Tier 1 is only 32bit i686 and 64bit x86_64. Tier 2 platforms can be thought of as “guaranteed to build”. Automated tests are not run so it’s not guaranteed to produce a working build.
- dagmx 8y agoIt's pretty par for the course to have tier 1 be the most common consumer systems since they're the ones with the most bang for buck, and easiest available CI infrastructure.
- steveklabnik 8y agoWe’ve been thinking about re-doing the tier system, as it misses some important points. For example, Firefox has ARM as a tier 1 platform, so if we find bugs, they tend to get fixed up pretty quick. We’re not sure the current way of defining stuff really maps to the reality.
- wyldfire 8y agoThis is AFAICT a rust developer consideration more than anything else? I think/hope that releases are gated by one or more tier 2's successful target tests?
- rcxdude 8y agoAFAIK this is mostly waiting on someone to step up and provide the relevant CI infrastructure.
- hsivonen 8y agoNotably for the topic at hand, RISC-V target list is unmerged: https://github.com/rust-lang/rust-forge/pull/202/files https://github.com/rust-lang/rust-forge/pull/202/files (Also two other unmerged PRs to the list.)
- steveklabnik 8y agoThanks for the heads up; I’ve merged that one. I’ll try to check out the others.