This is the mail archive of the gcc-patches@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] PATCH: Locate DWARF information in ELF files

From: Jakub Jelinek <jakub at redhat dot com>
To: Daniel Berlin <dberlin at dberlin dot org>
Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, mark at codesourcery dot com, gcc-patches at gcc dot gnu dot org
Date: Mon, 19 Jun 2006 02:17:19 -0400
Subject: Re: [lto] PATCH: Locate DWARF information in ELF files
References: <200606182025.k5IKP5vf013091@sparrowhawk.codesourcery.com> <C07A7E48-AD80-4984-AC97-A749507376C7@physics.uc.edu> <4495E672.9000300@dberlin.org>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Sun, Jun 18, 2006 at 07:49:06PM -0400, Daniel Berlin wrote:
> Uli has a replacement for it if you really want one.

Yes, elfutils is now GPLed as whole (previously libelf alone in it was dual
licensed GPL/OSL and the rest was OSL), so there really shouldn't be any
obstackles in using it.  libelf is certainly a good choice for lto ELF
reader.

> > Even some GNU/Linux does not
> > include libelf by default.  Why not use BFD to read the dwarf2 info  
> > instead?
> 
> Because BFD is such overkill for this that it's not even funny.
> libelf is much much simpler, and i think a good choice to start with.

Furthermore, BFD has no stable ABI, so it is quite hard for GCC to rely on
its ABI of the day, unless everybody is forced to using a combined
gcc+binutils tree.

	Jakub

References:
- [lto] PATCH: Locate DWARF information in ELF files
  - From: Mark Mitchell
- Re: [lto] PATCH: Locate DWARF information in ELF files
  - From: Andrew Pinski
- Re: [lto] PATCH: Locate DWARF information in ELF files
  - From: Daniel Berlin

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