rust/src/bootstrap/flags.rs, branch 1.63.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.63.02022-06-09T10:10:15+00:00Revert "Remove num_cpus dependency from bootstrap, build-manifest and rustc_session"2022-06-09T10:10:15+00:00David Tolnaydtolnay@gmail.com2022-06-09T10:10:15+00:00urn:sha1:1ae4b258267462da0b1aae1badcf83578153c799
This reverts commit 2d854f9c340df887e30896f49270ae81feb3e227.
Fully stabilize NLL2022-06-03T21:16:41+00:00Jack Huey31162821+jackh726@users.noreply.github.com2022-04-01T17:13:25+00:00urn:sha1:410dcc96741716bf1b4dc9b3bf33f408f220384dRollup merge of #97411 - raiyansayeed:print-stderr-consistently, r=Mark-Simulacrum2022-05-27T23:11:47+00:00Matthias Krügermatthias.krueger@famsik.de2022-05-27T23:11:47+00:00urn:sha1:1174dba02f8fdda0c8100879a612b94d4737c22f
Print stderr consistently
Solves https://github.com/rust-lang/rust/issues/96712
I tried to follow what I perceived as the general consensus for error messages in boostrap i.e messages that were ..
* resulting from an Err(...) =>
* literally called as "Error: ...."
* by the end of the block scope forced to run a panic! or process::exit with a guaranteed non-zero error code.
feat: refactored bootstrap files to use stderr consistently2022-05-26T02:01:55+00:00Raiyanraiyan.business@gmail.com2022-05-26T02:01:55+00:00urn:sha1:d25f64ae993dfdd6a55b912fa1d46a6085205d2bAdd test skip support2022-05-10T14:29:48+00:00Collin Bakercollinbaker@chromium.org2022-04-27T21:11:14+00:00urn:sha1:b2316c1a88b09dfebe7cabf889af9ceab8fef5f9
libtest already supports a "--skip SUBSTRING" arg which excludes any
test names matching SUBSTRING.
This adds a "--skip" argument to compiletest and bootstrap which is
forwarded to libtest.
Add a test for `--exclude test::XXX`2022-04-22T02:30:54+00:00Joshua Nelsonjnelson@cloudflare.com2022-04-22T02:29:37+00:00urn:sha1:7a4a66da3d5020311c78bdfbafad647fc99e436a
I didn't know that the `test::` syntax was valid before, and it doesn't
seem to be documented anywhere. Add a test so it doesn't regress accidentally,
and as executable documentation.
bootstrap: consolidate subcommand parsing and matching2022-04-16T18:54:17+00:00Allen Wildallenwild93@gmail.com2022-04-13T04:56:47+00:00urn:sha1:870cb8ef922dc6f4a1537572cd302e5a35e1869a
There's several places where the x.py command names are matched as
strings, leading to some inconsistencies and opportunities for cleanup.
* Add Format, Clean, and Setup variants to builder::Kind.
* Use Kind to parse the x.py subcommand name (including aliases)
* Match on the subcommand Kind rather than strings when handling
options and help text.
* Several subcommands don't display any paths when run with `-h -v` even
though the help text indicates that they should. Fix this and refactor
so that manually keeping matches in sync isn't necessary.
Fixes #95937
copy over `std::path::absolute` instead of adding `canonicalize` hacks2022-03-07T22:06:31+00:00Joshua Nelsonjnelson@cloudflare.com2022-03-03T12:12:32+00:00urn:sha1:477cae3bd7d71c347b3031809a153cfbeecd1c23
this also fixes a bug where bootstrap would try to use the fake `rustc` binary built by bootstrap -
cargo puts it in a different directory when using `cargo run` instead of x.py
fix weird bug when `out` would get overridden by unit tests2022-03-07T22:06:11+00:00Joshua Nelsonjnelson@cloudflare.com2022-02-07T03:24:47+00:00urn:sha1:984527f7bb49bd6e2d34e65d7629d2e0cdc464f6Don't depend on python for RUST_BOOTSTRAP_CONFIG2022-03-07T22:06:11+00:00Joshua Nelsonjnelson@cloudflare.com2022-02-07T00:10:49+00:00urn:sha1:62b522ec3a8967501466bfe8889fe54667c4e4d1