-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
change config.toml to bootstrap.toml #137081
change config.toml to bootstrap.toml #137081
Conversation
rustbot has assigned @Mark-Simulacrum. Use |
Failed to set assignee to
|
r? @onur-ozkan |
This comment has been minimized.
This comment has been minimized.
044bdca
to
58f42a6
Compare
39f2c36
to
e4506e0
Compare
Some changes occurred in compiler/rustc_codegen_gcc Some changes occurred in src/tools/compiletest cc @jieyouxu This PR modifies If appropriate, please update Some changes occurred to the CTFE machinery cc @rust-lang/wg-const-eval
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. This PR modifies cc @jieyouxu Some changes occurred in src/doc/rustc/src/platform-support cc @Noratrieb This PR modifies If appropriate, please update Some changes occurred in src/doc/unstable-book/src/compiler-flags/control-flow-guard.md cc @rust-lang/project-exploit-mitigations, @rcvalle Some changes occurred in compiler/rustc_codegen_cranelift cc @bjorn3 This PR changes how LLVM is built. Consider updating src/bootstrap/download-ci-llvm-stamp. The Miri subtree was changed cc @rust-lang/miri Some changes occurred in src/tools/opt-dist cc @Kobzol Some changes occurred to the CTFE / Miri interpreter cc @rust-lang/miri The rustc-dev-guide subtree was changed. If this PR only touches the dev guide consider submitting a PR directly to rust-lang/rustc-dev-guide otherwise thank you for updating the dev guide with your changes. cc @BoxyUwU, @jieyouxu, @Kobzol Some changes occurred in match checking cc @Nadrieril |
This looks like a rebase gone wild? You might try |
3c592fd
to
6b86aae
Compare
☔ The latest upstream changes (presumably #138506) made this pull request unmergeable. Please resolve the merge conflicts. |
1a43176
to
ea8b263
Compare
@jieyouxu Could you please take another look once you have time? This PR is very conflict prone and it's not approved right now, so it has to be rebased all the time. Thank you! |
☔ The latest upstream changes (presumably #138548) made this pull request unmergeable. Please resolve the merge conflicts. |
Sorry, not really available for reviews on larger PRs until next weekend due to medical reasons. |
Oh, ok! I will take a look then. Get well soon! |
Found some more occurrences of
|
ea8b263
to
9ef42ba
Compare
@bors r=onur-ozkan,jieyouxu,kobzol Thank you! Let's see what happens this time. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (8279176): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary 3.3%, secondary 6.4%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
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: 774.895s -> 775.979s (0.14%) |
…youxu Leave a breadcrumb towards bootstrap config documentation in `bootstrap.toml` I was curious as to the possible bootstrap options I can put in config.toml, but had some trouble figuring it out. There is no obvious documentation in `config.toml` (obviously), the documentation in src/bootstrap/defaults is *nice*, but also rather sparse, by design. I had to dive into the parsing code, and stuble upon [a very helpful doc comment](https://github.com/rust-lang/rust/blob/30f168ef811aec63124eac677e14699baa9395bd/src/bootstrap/src/core/config/config.rs#L181) there to realize that `config.example.toml` *exists*, and that it does, indeed, answer all of my questions. So I figured it might be worth making this journey a bit easier for future contributors and add mention the `config.example.toml` directly in `config.toml`. Now, since rust-lang#137081 is in-flight which would rename `config(.example)?.toml` to `bootstrap(.example)?.toml`, I figure it's better to wait until that one lands, and submit the "new", "correct" filename upfront, instead of landing `config.toml` now and updating it to `boostrap.toml` later. `@rustbot` blocked rust-lang#137081
Currently, both Bootstrap and Cargo uses same name as their configuration file, which can be confusing. This PR is based on a discussion to rename
config.toml
tobootstrap.toml
for Bootstrap. Closes: #126875.I have split the PR into atomic commits to make it easier to review. Once the changes are finalized, I will squash them. I am particularly concerned about the changes made to modules that are not part of Bootstrap. How should we handle those changes? Should we ping the respective maintainers?