-
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
Greatly reduce amount of debuginfo compiled for bootstrap itself #89756
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This feels a little adhoc and not terribly future proof. I think custom profiles are stable or will be quite soon, maybe we can use that?
FWIW I think we haven't had panics and such from bootstrap in a while, so maybe we can just disable debuginfo fully...
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 debuginfo useful when modifying bootstrap itself, but I guess it's not too hard to add it back in in bootstrap.py if necessary. I don't think it would make this much simpler though, we definitely don't want to disable debuginfo for anything besides bootstrap.
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.
Hmm, adding the
named-profiles
feature breaks x.py because it doesn't pass RUSTC_BOOTSTRAP for building bootstrap itself. Also I think this would prevent people from runningcargo metadata
with anything other than nightly.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.
@jyn514 Is it currently guaranteed that e.g. running
cargo metadata
onrustc
with a stable compiler will always work? For example right now it doesn't work, because the stable compiler misses edition 2021, which is used bysrc/bootstrap/Cargo.toml
.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.
It's not guaranteed, but it does work most of the time.
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.
OK, I've thought a little more about this and it seems OK to me to do this as-is. It's fairly minimal still, and hopefully as you say won't affect anything else. We could try to be a little more minimal by setting this via the env variable (
CARGO_PROFILE_<name>_DEBUG
) but it doesn't seem particularly necessary so we can just do this for now.