diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2025-08-04 11:24:41 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-04 11:24:41 +1000 |
| commit | 22653b8c1eec0e3cf89a8039fd9d350fee2eb732 (patch) | |
| tree | 0dcd05919541f3e9d5bc9e9a4d06c34a5d952201 /src/doc/rustc-dev-guide/examples/rustc-driver-example.rs | |
| parent | 79e7e0359e57d88f62d2eb0280fd9de4d7de93ce (diff) | |
| parent | 3abbdffdbfe05a596e59dbd6d81a4f17e4d68044 (diff) | |
| download | rust-22653b8c1eec0e3cf89a8039fd9d350fee2eb732.tar.gz rust-22653b8c1eec0e3cf89a8039fd9d350fee2eb732.zip | |
Rollup merge of #144848 - Zalathar:ui-fulldeps, r=clubby789
For "stage 1" ui-fulldeps, use the stage 1 compiler to query target info Testing ui-fulldeps in "stage 1" actually uses the stage 0 compiler, so that test programs can link against stage 1 rustc crates. Unfortunately, using the stage 0 compiler causes problems when compiletest tries to obtain target information from the compiler, but the output format has changed since the last bootstrap beta bump. We can work around this by also providing compiletest with a stage 1 compiler, and having it use that compiler to query for target information. --- This fixes the stage 1 ui-fulldeps failure seen at https://github.com/rust-lang/rust/pull/144443#issuecomment-3146992771.
Diffstat (limited to 'src/doc/rustc-dev-guide/examples/rustc-driver-example.rs')
0 files changed, 0 insertions, 0 deletions