[cfe-dev] Generating index file for CTU analysis

Kristóf Umann via cfe-dev cfe-dev at lists.llvm.org
Mon Apr 1 09:12:08 PDT 2019


Adding some folks more knowledgeable on this topic :) Gábor, Endre, do you
know what's the issue here? Do we have this documented somewhere?

On Sat, 30 Mar 2019 at 01:16, Gavin Cui via cfe-dev <cfe-dev at lists.llvm.org>
wrote:

> Hi, I was trying to play with the cross translation unit analysis by
> passing the argument '-analyzer-config
> experimental-enable-naive-ctu-analysis=true'.  However, it seems I need to
> generate an 'externalDefMap.txt' file at first. Then I found that I may be
> able to use 'intercept-build <build-command>' and 'analyze-build
> --ctu-collect-only' script for generating this file.
>
> I currently stack at the intercept build step,
> But after running 'intercept-build gcc -o test test.c foo.c', I got an
> empty 'compile_commands.json' file.
>
> How could I address this problem or is there any other way to generate the
> CTU index file?
> Thank you!
>
> Regards!
>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20190401/3848e26b/attachment.html>


More information about the cfe-dev mailing list