MaskRay added a comment. Assuming scan-build is clang/tools/scan-build, which is in tree and can be fixed instead. I am not familiar with it, but from
> However, this caused issues with scan-build, as GCC is used as the compiler > but clang is invoked after it with all the -f options that GCC was. if scan-build+GCC takes all GCC recognized options and forwards them to Clang, I think it is a generally infeasible model. GCC has dozens of options not recognized by Clang... Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D117717/new/ https://reviews.llvm.org/D117717 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
