You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often you are in a situation where you want to try some modifications of some basic library like libcore or some other library with the stage1 compiler, without rebuilding stage1.
A param like --assume-stage=n passed to rustbuild which doesn't (re-)build stage n artifacts would be really neat for this.
@bluss had the original idea, and it would be really useful for development on the i128 PR as well: there, large parts of the libcompiler_builtins crate are under #[cfg(not(stage0))], so I'm only interested in what happens in higher stages when modifying them.
The text was updated successfully, but these errors were encountered:
bluss
added
the
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
label
Dec 12, 2016
rustbuild: Add cli option --keep-stage
This option is intended to be used like:
./x.py build --stage 1 --keep-stage 0
Which skips all stage 0 steps, so that stage 1 can be recompiled
directly (even if for example libcore has changes).
This is useful when working on `cfg(not(stage0))` parts of the
libraries or when re-running stage 1 tests in libraries in general.
Fixes#38326
Often you are in a situation where you want to try some modifications of some basic library like libcore or some other library with the stage1 compiler, without rebuilding stage1.
A param like
--assume-stage=n
passed to rustbuild which doesn't (re-)build stage n artifacts would be really neat for this.@bluss had the original idea, and it would be really useful for development on the i128 PR as well: there, large parts of the libcompiler_builtins crate are under
#[cfg(not(stage0))]
, so I'm only interested in what happens in higher stages when modifying them.The text was updated successfully, but these errors were encountered: