-
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
std: Update wasi-libc commit of the wasm32-wasi target #79578
Conversation
r? @shepmaster (rust-highfive has picked a reviewer for you, use r? to override) |
Before approving this, could I get infra team assistance to mirror https://github.com/llvm/llvm-project/releases/download/llvmorg-11.0.0/clang+llvm-11.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz into the CI bucket? |
Oh dear looks like I forgot about this. @shepmaster are you up for reviewing this? If not do you know how I can request another reviewer? |
Ha, found this while checking if there are open PRs to integrate the current dir functionality. @alexcrichton glad you're on top of it :) |
@bors r+ |
📌 Commit fc1ae1a has been approved by |
std: Update wasi-libc commit of the wasm32-wasi target This brings in an implementation of `current_dir` and `set_current_dir` (emulation in `wasi-libc`) as well as an updated version of finding relative paths. This also additionally updates clang to the latest release to build wasi-libc with.
Failed in rollup:
@bors r- |
@bors rollup=iffy |
@pietroalbini or @Mark-Simulacrum, would one of y'all be able to mirror the tarball above on s3? |
hm, https://github.com/llvm/llvm-project/releases/download/llvmorg-11.0.0/clang+llvm-11.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz appears to 404 for me - I used https://github.com/llvm/llvm-project/releases/download/llvmorg-11.0.1/clang+llvm-11.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz as we've updated to 11.0.1 now I think and uploaded that to (%2B appears to be important; regular + won't work) |
fc1ae1a
to
7eb0c7b
Compare
@bors: r=KodrAus Thanks @Mark-Simulacrum! FWIW there's no need for a version match here, this is just the toolchain used to build wasi itself, which isn't cross-lang-LTO'd or anything like that. |
📌 Commit 7eb0c7b7a144d449aeff271dd908e0263026e074 has been approved by |
The job Click to see the possible cause of the failure (guessed by this bot)
|
This brings in an implementation of `current_dir` and `set_current_dir` (emulation in `wasi-libc`) as well as an updated version of finding relative paths. This also additionally updates clang to the latest release to build wasi-libc with.
7eb0c7b
to
5756bd7
Compare
@bors: r=KodrAus |
📌 Commit 5756bd7 has been approved by |
⌛ Testing commit 5756bd7 with merge 7216bd0e3154fa9257c58622155c29d951e0b966... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors: retry |
⌛ Testing commit 5756bd7 with merge 4d2eda19ac863963a6fb714196c031eb4a742b61... |
💔 Test failed - checks-actions |
@bors: retry |
☀️ Test successful - checks-actions |
This brings in an implementation of
current_dir
andset_current_dir
(emulation in
wasi-libc
) as well as an updated version of findingrelative paths. This also additionally updates clang to the latest
release to build wasi-libc with.