[PATCH] D72982: [Clang] Un-break scan-build after integrated-cc1 change
Gábor Horváth via Phabricator via cfe-commits
cfe-commits at lists.llvm.org
Tue Jan 21 11:46:27 PST 2020
xazax.hun added a comment.
In D72982#1832029 <https://reviews.llvm.org/D72982#1832029>, @aganea wrote:
> In D72982#1832000 <https://reviews.llvm.org/D72982#1832000>, @xazax.hun wrote:
>
> > Thanks! Alternatively we could try to push the changes to all three versions and revert this patch once all of them are accepted and a new pip package is published.
>
>
> @xazax.hun In that case do you think it'd be possible for scan-build to handle a more structured format like a CDB? (and inherently make clang emit that)
In case you refer to compilation database, scan-build-py already does handle that. The cc1 command line is used to avoid duplicating driver logic in scan-build. So sometimes, when scan-build want to peak the cc1 commands it will get it using `-###` instead of trying to infer them from the (driver) command that is available in the compilation database.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D72982/new/
https://reviews.llvm.org/D72982
More information about the cfe-commits
mailing list