Distribute cg_clif as rustup component on the nightly channel#81746
Distribute cg_clif as rustup component on the nightly channel#81746bors merged 5 commits intorust-lang:masterfrom
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
077c3ee to
b64122f
Compare
This comment has been minimized.
This comment has been minimized.
b64122f to
06d3150
Compare
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
8b5ccb9 to
c341ecf
Compare
|
For the bootstrap tests, I'd recommend an x.py build locally that tries to reproduce it (--dry-run should help with getting quick results), and running with -vvv to see what is invoking the newly added rustc builds. I suspect it's something in the codegenbackend step in compile.rs, but haven't investigated myself (and would prefer not to). |
Thanks for the tip! I got this with Disabling it fixes the problem. |
c341ecf to
cd173e6
Compare
|
Previously it would build assemble stage 1 -> (rustc stage 0 and codegen backend stage 0) and std stage 1. Now it also builds codegen backend stage 1 -> rustc stage 1. Removing the |
|
Let's check if the rustup component is correctly generated. @bors try |
|
⌛ Trying commit 909dbc1857b49279156b64061c13ab55c9f03b80 with merge 4bbf0fa74cbc11268c4f6f9d641e12b360065fc1... |
|
☀️ Try build successful - checks-actions |
|
I must have made a mistake somewhere. |
|
I think I should wire up |
|
@bors try |
|
⌛ Trying commit de705b10023b1ed5b9ad92810e3a0ea1dc29caee with merge 874d9737dc9cca284c21e5b4aaf40bf57502947f... |
|
☀️ Try build successful - checks-actions |
|
And to try if I didn't break anything on linux: @bors try |
|
☀️ Try build successful - checks-actions |
|
@Mark-Simulacrum could I get another review? Only the last commit is new compared to the last attempt at merging. |
|
@bors r+ |
|
☀️ Test successful - checks-actions |
|
This PR was opened 2½ years ago, on Feb 4 2021. Huge congratulations @bjorn3, for this amazing achievement (and it's only the beginning). |
|
Outstanding work! I look forward to using this. Be proud 🥳 |
|
I found two issues:
Currently trying to find the cause of both issues. Edit: #117328 seems to be a fix for both issues. |
|
Finished benchmarking commit (6a66ca2): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 636.535s -> 637.097s (0.09%) |
|
I can't be the only one with this question - how does one actually put this to use after Edit: I thought #117328 landed by |
That looks like you are mixing the cranelift codegen backend component with the compilation target toolchain.
As github sais this was merged two days ago I would have expected this to be in the current nightly and based on the PR description I would expect the following to work
1b and 2 succeeded the later suprisingly quickly, but 3 failed with |
|
The build of the cranelift component wasn't working in this PR. It was fixed in #117328, so it should hopefully work in tomorrow's nightly. |
I think
Opened two days ago but merged 15 hours ago |
|
|
|
2023-10-30 nightly indeed works! |
|
@tgross35 https://bjorn3.github.io/2023/10/31/progress-report-oct-2023.html also describes the couple of other ways you can use cargo's support for selecting the backend to use. |
This makes it possible to use cg_clif using:
$ rustup component add rustc-codegen-cranelift-preview --toolchain nightly $ RUSTFLAGS="-Zcodegen-backend=cranelift" cargo +nightly buildcc rust-lang/compiler-team#405.
r? @Mark-Simulacrum