mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-25 20:23:11 +01:00
f5f29ea8b3
`FILECHECK_OPTS` was implemented so that a test runner, such as CI, can specify FileCheck debugging options, such as `-v` and `-vv`. However, if a test suite has a FileCheck call that already specifies `-v` or `-vv`, then that call will fail if `FILECHECK_OPTS` also specifies it. For `-vv`, this problem already exists: `clang/test/CodeGen/aarch64-v8.2a-fp16-intrinsics-constrained.c` It's not yet clear if the `-vv` in that test was intentional, but this usage shouldn't fail anyway. It's already true that FileCheck permits `-vv` and `-v` together even though `-vv` implies `-v`. Compare D70784, which fixed the same problem for `-dump-input`. Reviewed By: jhenderson, thopre Differential Revision: https://reviews.llvm.org/D82601 |
||
|---|---|---|
| .. | ||
| Analysis | ||
| Assembler | ||
| Bindings | ||
| Bitcode | ||
| BugPoint | ||
| CodeGen | ||
| DebugInfo | ||
| Demangle | ||
| Examples | ||
| ExecutionEngine | ||
| Feature | ||
| FileCheck | ||
| Instrumentation | ||
| Integer | ||
| JitListener | ||
| Linker | ||
| LTO | ||
| MachineVerifier | ||
| MC | ||
| Object | ||
| ObjectYAML | ||
| Other | ||
| Reduce | ||
| SafepointIRVerifier | ||
| Support | ||
| SymbolRewriter | ||
| TableGen | ||
| ThinLTO/X86 | ||
| tools | ||
| Transforms | ||
| Unit | ||
| Verifier | ||
| YAMLParser | ||
| .clang-format | ||
| CMakeLists.txt | ||
| lit.cfg.py | ||
| lit.site.cfg.py.in | ||
| TestRunner.sh | ||