diff options
| author | bors <bors@rust-lang.org> | 2024-01-07 00:32:24 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-01-07 00:32:24 +0000 |
| commit | 78c988fe3e497d181ddc07ba954f902c1cf1d480 (patch) | |
| tree | fb9557bf8026d09e86858d56130f38f864006855 /compiler/rustc_codegen_gcc | |
| parent | fde0e98247dd4dd13af6cfe21f9eab2e54d50f12 (diff) | |
| parent | 735a6a4212eb658b59564bf5bdc3adc28afc6c75 (diff) | |
| download | rust-78c988fe3e497d181ddc07ba954f902c1cf1d480.tar.gz rust-78c988fe3e497d181ddc07ba954f902c1cf1d480.zip | |
Auto merge of #119035 - saethlin:remove-linker-requirement, r=onur-ozkan
Run Miri and mir-opt tests without a target linker Normally, we need a linker for the target to build the standard library. That's only because `std` declares crate-type lib and dylib; building the dylib is what creates a need for the linker. But for mir-opt tests (and for Miri) we do not need to build a `libstd.so`. So with this PR, when we build the standard library for mir-opt tests, instead of `cargo build` we run `cargo rustc --crate-type=lib` which overrides the configured crate types in `std`'s manifest. I've also swapped in what seems to me a better hack than `BOOTSTRAP_SKIP_TARGET_SANITY` to prevent cross-interpreting with Miri from checking for a target linker and expanded it to mir-opt tests too. Whether it's actually better is up to a reviewer.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions
