-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Omit the vendor component in the WASI triple #60585
Conversation
To confirm, this is the same naming scheme the clang is moving towards, right? I think it makes sense to ensure that we're consistent across the board there! |
Clang and LLVM themselves accept either form -- the logic to do this is target-independent. But otherwise yeah, we're generally moving to "wasm32-wasi" in documentation, build scripts, and tests. |
@bors: r+ Ok sounds good to me! I think it makes sense to follow the same conventions across the board wherever possible. |
📌 Commit 58624ed has been approved by |
…hton Omit the vendor component in the WASI triple This renames wasm32-unknown-wasi to wasm32-wasi, omitting the vendor component. This follows aarch64-linux-android, x86_64-fuchsia, and others in omitting the vendor field, which has the advantage of aligning with the [multiarch tuple](https://wiki.debian.org/Multiarch/Tuples), and of being less noisy. r? @alexcrichton
…hton Omit the vendor component in the WASI triple This renames wasm32-unknown-wasi to wasm32-wasi, omitting the vendor component. This follows aarch64-linux-android, x86_64-fuchsia, and others in omitting the vendor field, which has the advantage of aligning with the [multiarch tuple](https://wiki.debian.org/Multiarch/Tuples), and of being less noisy. r? @alexcrichton
@bors r- We can't update the dist-various-2 image since it's on an EOL Ubuntu release (17.10). Can you try to bump it to 18.04? |
Thanks! @bors r=alexcrichton rollup=never |
📌 Commit 84e3d8e479551c8d73a9753954ea1856265c1bf3 has been approved by |
⌛ Testing commit 84e3d8e479551c8d73a9753954ea1856265c1bf3 with merge 63ff0da517271bb0dd1e027b322e3364ae2b8573... |
Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-travis |
I'm working on a PR to properly upgrade that image to Ubuntu 18.04. |
Blocked on #60665. Also, can you remove the Ubuntu version bump commit? It's already included in the PR I linked. |
This renames wasm32-unknown-wasi to wasm32-wasi, omitting the vendor component. This follows aarch64-linux-android, x86_64-fuchsia, and others in omitting the vendor field, which has the advantage of aligning with the [multiarch tuple](https://wiki.debian.org/Multiarch/Tuples), and of being less noisy.
Ok, I removed the Ubuntu version bump commit. |
Not blocked anymore 🎉 @bors r=alexcrichton rollup=never |
📌 Commit 1fe3ce1 has been approved by |
Omit the vendor component in the WASI triple This renames wasm32-unknown-wasi to wasm32-wasi, omitting the vendor component. This follows aarch64-linux-android, x86_64-fuchsia, and others in omitting the vendor field, which has the advantage of aligning with the [multiarch tuple](https://wiki.debian.org/Multiarch/Tuples), and of being less noisy. r? @alexcrichton
☀️ Test successful - checks-travis, status-appveyor |
- WASI is now categorized as an OS rather than an environment. (rust-lang/rust#60117) - The WASI triple is renamed from wasm32-unknown-wasi to wasm32-wasi. (rust-lang/rust#60585)
This renames wasm32-unknown-wasi to wasm32-wasi, omitting the vendor
component. This follows aarch64-linux-android, x86_64-fuchsia, and others in
omitting the vendor field, which has the advantage of aligning with the
multiarch tuple, and of being
less noisy.
r? @alexcrichton