This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [LTO] LTO breaks if debug info is stripped from object files
- From: David Edelsohn <dje at watson dot ibm dot com>
- To: Diego Novillo <dnovillo at google dot com>
- Cc: William Maddox <maddox at google dot com>, gcc at gcc dot gnu dot org, Kenneth Zadeck <zadeck at naturalbridge dot com>, Mark Mitchell <mark at codesourcery dot com>
- Date: Fri, 16 Nov 2007 15:27:29 -0500
- Subject: Re: [LTO] LTO breaks if debug info is stripped from object files
- References: <8a0e66f0711151453u1f347dedl788518f5a1ff8475@mail.gmail.com> <473DF783.5070804@google.com>
>>>>> Diego Novillo writes:
Diego> I'm not sure if it's intended, but I don't think it's desirable. The
Diego> information needed to do LTO optimizations should be independent from
Diego> the debugging information.
Diego> We could have a --strip-lto option for strip, but I don't think
Diego> --strip-debug should remove LTO data.
Having LTO dwarf information dependent on debugging section may
not be great, but is the alternative better? If we place the lto dwarf
info in another section, should debuggers also look there? Or should we
duplicate info in both .debug and .lto, which bloats the file? Or should
binutils look for .to and not strip .debug or warn about stripping .debug
affecting LTO?
David