================ @@ -1,23 +1,10 @@ // RUN: rm -rf %t // RUN: split-file %s %t -//--- missing_tu.json.in -[{ - "directory": "DIR", - "command": "clang -fsyntax-only DIR/missing_tu.c", - "file": "DIR/missing_tu.c" -}] -//--- missing_header.json.in -[{ - "directory": "DIR", - "command": "clang -fsyntax-only DIR/missing_header.c", - "file": "DIR/missing_header.c" -}] //--- missing_header.c #include "missing.h" -// RUN: sed -e "s|DIR|%/t|g" %t/missing_tu.json.in > %t/missing_tu.json -// RUN: not clang-scan-deps -compilation-database %t/missing_tu.json 2>%t/missing_tu.errs +// RUN: not clang-scan-deps -- "clang" %t/missing_tu.c 2>%t/missing_tu.errs ---------------- benlangmuir wrote:
> Since the scanner is intended to be run on actual compilation jobs, I think > it's even desirable removing stuff like "-fsyntax-only". Changing -fsyntax-only to -c would make sense then, but it's weird to me to have linker steps in scanning unless that's specifically what you're testing. Anyway, since this one fails before it gets there I guess it doesn't matter, but I wouldn't want to see tests defaulting to linking. https://github.com/llvm/llvm-project/pull/88764 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits