This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [LTO] LTO breaks if debug info is stripped from object files

From: Diego Novillo <dnovillo at google dot com>
To: William Maddox <maddox at google dot com>
Cc: 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:03:15 -0500
Subject: Re: [LTO] LTO breaks if debug info is stripped from object files
References: <8a0e66f0711151453u1f347dedl788518f5a1ff8475@mail.gmail.com>

William Maddox wrote:

It appears that portions of the LTO information are emitted in the usual
debugging sections, rather, information that would already be present there
is shared.  This is great for reducing the size of object files that
contain both
LTO info and debugging info, but means that LTO breaks if 'strip --strip-debug'
has been run on object files submitted to it as input. Is this intended or
desirable behavior?

I'm not sure if it's intended, but I don't think it's desirable. The information needed to do LTO optimizations should be independent from the debugging information.

We could have a --strip-lto option for strip, but I don't think --strip-debug should remove LTO data.

Mark, Kenny, your thoughts?

Diego.

Follow-Ups:
- Re: [LTO] LTO breaks if debug info is stripped from object files
  - From: David Edelsohn
- Re: [LTO] LTO breaks if debug info is stripped from object files
  - From: Daniel Jacobowitz

References:
- [LTO] LTO breaks if debug info is stripped from object files
  - From: William Maddox

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]