-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Update comment for STAGE0_MISSING_TARGETS
#149840
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
Conversation
|
The Miri subtree was changed cc @rust-lang/miri |
|
rustbot has assigned @Mark-Simulacrum. Use |
|
@rustbot blocked |
This comment was marked as resolved.
This comment was marked as resolved.
36fe951 to
48d34c9
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
Rerolling since Mark has like 30 in-review PRs |
75e9176 to
bc4737d
Compare
|
Nit: Since we're modifying this whole comment, could you also replace the |
src/bootstrap/src/core/sanity.rs
Outdated
| // Targets can be removed from this list once they are present in the stage 0 compiler during a | ||
| // bootstrap compiler bump (typically updating the bootstrap compiler to a newer beta compiler that | ||
| // *does* already know about the targets). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find this phrasing a bit confusing.
Is the idea that people should feel free to update this list as part of a bootstrap beta bump, if the new stage0 compiler now knows about the missing targets?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the idea is that it'll happen during the usual release process bootstrap compiler bumps. But such bumps can also rarely happen manually outside of the usual release procedures (I've done that once or twice I think?) but definitely not for updating missing stage 0 target reasons.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed it to say
Targets can be removed from this list during the usual release process bootstrap compiler bumps.
... which, I don't know, might be worse?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would at least want to mention again why they can be removed, i.e. because the newly-bumped stage0 compiler now knows about the formerly-missing targets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added that remark in de0945b
bc4737d to
00013a0
Compare
00013a0 to
de0945b
Compare
|
Looks good; r=me if you're done making edits. |
|
@bors r=Zalathar rollup |
…uwer Rollup of 4 pull requests Successful merges: - #149840 (Update comment for `STAGE0_MISSING_TARGETS`) - #150109 (crash test readme: point to rustc-dev-guide) - #150204 (Port `#[cfi_encoding]` to attribute parser) - #150237 (Skip tidy target-specific check for `run-make-cargo` too) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of #149840 - jieyouxu:bootstrap-missing-stage0, r=Zalathar Update comment for `STAGE0_MISSING_TARGETS`
No description provided.