=?utf-8?q?Félix-Antoine?= Constantin Message-ID: In-Reply-To: <llvm.org/llvm/llvm-project/pull/111...@github.com>
carlosgalvezp wrote: The way we do it at our place is that we have 2 toolchains, one for GCC and one for Clang, each with separate sets of flags. We assume that being able to compile with Clang is a prerequisite to running clang-tidy. For example, even if you have only `-Wall`, Clang (via clang-tidy) could introduce a warning that GCC doesn't have, so you'd get Clang compiler errors via clang-tidy (`clang-diagnostic-error`), which is confusing. Once that's satisfied, we can run clang-tidy based on the Clang toolchain - this way we ensure all the flags are valid for clang-tidy (since they are for Clang). But I understand if having 2 parallel toolchains can be costly to maintain. https://github.com/llvm/llvm-project/pull/111453 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
