[LLVMdev] memory hog llvm-ld

[Daniel Berlin]

On 7/19/07, Duncan Sands <baldrick at free.fr> wrote:
> Hi Holger,
>
> On Thursday 19 July 2007 12:57:40 Holger Schurig wrote:
> > > LLVM represents debug info as explicit calls to intrinsics.
> > > This approach has many advantages, but a possible disadvantage
> > > is that it can significantly increase the size of the bitcode.
> > > I don't know if that explains your observations.  I'm curious
> > > to know how gcc stores debug info...
> >
> > GCC stores debug info in ELF sections of the .o file, e.g.:
>
> so does LLVM!  I meant, how does gcc store debug info before
> it gets output to the object file, i.e. where does it live
> during the optimization passes, and in what format?
>

It doesn't.


It is generated after optimizations are performed (though we do track
some things through optimizations).