diff options
| author | Samuel Tardieu <sam@rfc1149.net> | 2025-08-02 11:24:27 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-02 11:24:27 +0200 |
| commit | 7a64c130f342fa23f67cf81bec76bb204c38fdaf (patch) | |
| tree | c4bf03e78d5326bb52b914a1269dcfed2e70a7cd /compiler/rustc_llvm | |
| parent | 5b8118495e698aa1ac9528fe411f99d0d1d3b5b9 (diff) | |
| parent | bd7b8b3612f8b62d215cac218f752a28eada7d7e (diff) | |
| download | rust-7a64c130f342fa23f67cf81bec76bb204c38fdaf.tar.gz rust-7a64c130f342fa23f67cf81bec76bb204c38fdaf.zip | |
Rollup merge of #144782 - jieyouxu:compiletest-selftests, r=Kobzol
Properly pass path to staged `rustc` to `compiletest` self-tests Otherwise, this can do weird things like use a global rustc, or try to use stage 0 rustc. This must be properly configured, because `compiletest` is intended to only support one compiler target spec JSON format (of the in-tree compiler). Historically, this was probably done so before `bootstrap` was really its own thing, and `compiletest` had to be runnable as a much more "self-standing" tool. Follow-up to rust-lang/rust#144675, as I didn't realize this until Zalathar pointed it out in [#t-infra/bootstrap > Building vs testing `compiletest` @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/Building.20vs.20testing.20.60compiletest.60/near/532040838). r? ````@Kobzol````
Diffstat (limited to 'compiler/rustc_llvm')
0 files changed, 0 insertions, 0 deletions