diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2025-07-30 17:59:37 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-30 17:59:37 +1000 |
| commit | b6ac83d372165421e1b14ea742dc4ed41bdef92b (patch) | |
| tree | 1e7f49d2d5dffc3b3713deaadaa65da950e343b6 /compiler/rustc_codegen_llvm/src | |
| parent | 919c40924373c248315a76618d8c52d39aed5e6e (diff) | |
| parent | cffde732ceecd1bcb333d34fe7a9c9caa4d9a9fa (diff) | |
| download | rust-b6ac83d372165421e1b14ea742dc4ed41bdef92b.tar.gz rust-b6ac83d372165421e1b14ea742dc4ed41bdef92b.zip | |
Rollup merge of #144042 - dpaoliello:verifyllvmcomp, r=jieyouxu
Verify llvm-needs-components are not empty and match the --target value I recently discovered a test with an empty `llvm-needs-components` entry (fixed in rust-lang/rust#143979) which meant that it didn't work correctly when building Rust with a limited set of LLVM targets. This change makes a pair of improvements to prevent this issue from creeping in again: * When parsing directives with values, `compiletest` will now raise an error if there is an empty value. * Improved the `target_specific_tests` tidy checker to map targets to LLVM components, to verify that any existing `llvm-needs-components` contains the target being used. I also fixed all the issues flagged by the improved tidy checker.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
