diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2025-04-08 20:55:08 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-04-08 20:55:08 +1000 |
| commit | ab80f575c485eccd57a86a92a7aabad5815270d7 (patch) | |
| tree | 5c8d3892455a7be5c3f437efc8c12d16446022af /compiler/rustc_codegen_llvm/src | |
| parent | 133cec736358347f5eea34d28fa0e1a9ced48f9d (diff) | |
| parent | cae28b5119cdb23544a80fafd02f486fdfe1183b (diff) | |
| download | rust-ab80f575c485eccd57a86a92a7aabad5815270d7.tar.gz rust-ab80f575c485eccd57a86a92a7aabad5815270d7.zip | |
Rollup merge of #139386 - onur-ozkan:configurable-compiletest-libtest, r=jieyouxu,kobzol
make it possible to use stage0 libtest on compiletest With https://github.com/rust-lang/rust/pull/119899, building the library tree will require a stage 1 compiler. This is because `compiletest` is defined as a `ToolStd` (since https://github.com/rust-lang/rust/pull/68019) in order to use the in-tree library. As a result, https://github.com/rust-lang/rust/pull/119899 makes certain development workflows more difficult as changes on the compiler tree will now require recompiling `compiletest` each time. This PR allows switching `ToolStd` to `ToolBootstrap` with a simple boolean option in `bootstrap.toml` to allow `compiletest` to use the stage 0 `libtest` instead. The changes under `src/ci` are clearly intended to make sure that `compiletest` doesn't break during future bootstrap beta bumps.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions