diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2024-02-26 10:27:41 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-26 10:27:41 +0100 |
| commit | 0e08be5360f9412c2a6fed52425f23f22db54ca5 (patch) | |
| tree | 743402f74a38cb114f0cfd218e7a2257e28d51c5 /compiler/rustc_codegen_llvm | |
| parent | dc00e8cdb6cfb6c75b4e98cdc181583cb7d11749 (diff) | |
| parent | e56cc8408d67afe5d58cdd4311ecc97ed44f14aa (diff) | |
| download | rust-0e08be5360f9412c2a6fed52425f23f22db54ca5.tar.gz rust-0e08be5360f9412c2a6fed52425f23f22db54ca5.zip | |
Rollup merge of #120656 - Zalathar:filecheck-flags, r=wesleywiser
Allow tests to specify a `//@ filecheck-flags:` header This allows individual codegen/assembly/mir-opt tests to pass extra flags to the LLVM `filecheck` tool as needed. --- The original motivation was noticing that `tests/run-make/instrument-coverage` was very close to being an ordinary codegen test, except that it needs some extra logic to set up platform-specific variables to be passed into filecheck. I then saw the comment in `verify_with_filecheck` indicating that a `filecheck-flags` header might be useful for other purposes as well.
Diffstat (limited to 'compiler/rustc_codegen_llvm')
0 files changed, 0 insertions, 0 deletions