-
Notifications
You must be signed in to change notification settings - Fork 13.3k
redesign stage 0 std #119899
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
Open
onur-ozkan
wants to merge
19
commits into
rust-lang:master
Choose a base branch
from
onur-ozkan:redesign-stage0-std
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+238
−262
Open
redesign stage 0 std #119899
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
64afccf
use initial rustc's std on stage 0
onur-ozkan f6f6bb0
remove cfg bootstrap from library tree
onur-ozkan 42e736e
update std uplifting algorithm
onur-ozkan 9ef0f10
improve `check::Std` handling
onur-ozkan b556705
handle cfg bootstrap on compiler and compiler tools
onur-ozkan 8888d39
handle rustc_span unsafe blocks
onur-ozkan accbfc0
update stage defaults
onur-ozkan f6f081c
bless bootstrap tests
onur-ozkan 213599c
use stage 1 for std on CI
onur-ozkan 787c796
split `mingw-check` into two
onur-ozkan d4db995
update dev guidelines
onur-ozkan df5a001
add change-entry
onur-ozkan 374eb93
improve comments and docs
onur-ozkan 37dbc32
add "library" to `RUSTC_IF_UNCHANGED_ALLOWED_PATHS`
onur-ozkan dd3ca61
be able to build stage1 library with CI-rustc
onur-ozkan 29e1bcb
fix CI-rustc bugs
onur-ozkan 6280bef
update `cfg(bootstrap)`s
onur-ozkan f98f710
fix CI errors
onur-ozkan d6f178a
fix fs bug on CI
onur-ozkan 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
I just learned about
compiletest-use-stage0-libtest
. Does this PR maketrue
the default value for that? It seems like there's no good reason to even still supportfalse
for that option, or is there?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.
true
might make sense as a default (since libtest programmatic API changes relatively unfrequently), but if someone is working on alibtest
(programmatic API) change that can require changingcompiletest
, in which case the contributor would probably want to usefalse
so that they can test their changes for compiletest too.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.
The default value for that option is already
true
andfalse
is useful to detect breaking changes from libtest to compiletest. Currently we runx check compiletest
withcompiletest-use-stage0-libtest=false
on couple of CI runners to prevent that.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.
The reason I thought it was "false" is that the change notification says
"Added a new option
build.compiletest-use-stage0-libtest
to forcecompiletest
to use the stage 0 libtest."That sure sounds like if I want compiletest to use stage 0 libtest I need to "force" that to happen by manually changing the configuration.