[cfe-dev] How does scan-build

Christian Gagneraud via cfe-dev cfe-dev at lists.llvm.org
Thu Jul 18 04:30:49 PDT 2019

On Thu, 18 Jul 2019 at 23:14, Дилян Палаузов <dpa-llvm at aegee.org> wrote:
> Hello Chirstian,
> for the rationale to join several input files into one, and pass that one to the static analyzer, see the thread Subj:
> “Many .c files as input to scan-build” Thread-Id: <e0b6149d092be2f191052aed11be0d2bf7b83d2a.camel at aegee.org> . The idea
> is to get more useful results out of the static analyzer by providing it with more complete picture of everything: a
> single source file containg all information.
> As far as LTO is concerned, it is not ready for the prime time.  In order of ar, nm and ranlib to work with LTO, the
> installation process of clang must install LLVMgold.so under ${libdir}/bfd-plugins otherwise the build system has to do
> a lot of magic and most build systems don’t do that magic (part of the magic is to call on some systems gcc-ar-5 and on
> others gcc-ar-5.0 or alike.  In fact cmake is the only build system to implement this magic completely, as of January
> 2019).  Build systems want to use just ar or nm.  I posted this to llvm-dev,
> http://lists.llvm.org/pipermail/llvm-dev/2018-March/122018.html and there is no interest to fix this.  Neither is there
> interest on gcc’s side.

Sorry, i haven't read any of the links above. Have you tried to simply
get rid of GNU binutils/gcc?
eg, use llvm all the way? -fuse-ld=lld and the likes? My experience
with gcc LTO (+dwarf) is so far pretty bad:
Just to name a few,I'm sure there are more.

More information about the cfe-dev mailing list