[GOLD] debug_msg test
Alan Modra
amodra@gmail.com
Fri Mar 8 00:45:00 GMT 2013
More information about the Binutils mailing list
Fri Mar 8 00:45:00 GMT 2013
- Previous message (by thread): [GOLD] debug_msg test
- Next message (by thread): [GOLD] debug_msg test
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Mar 07, 2013 at 10:59:57AM -0800, Cary Coutant wrote: > > Yes, I'm sure we don't have a problem with the dwarf info. (Or at > > least, it's not an easy problem to fix.) PowerPC64 doesn't have a > > linker managed GOT like most other targets. Instead the compiler > > manages the GOT (and calls it TOC). That results in no relocation > > on the actual code referencing a variable, but one in the TOC section > > instead. Like a linker managed GOT, a TOC entry can serve multiple > > references to a given symbol, so there isn't really any way to > > associate a TOC entry with a particular source/line. I suppose we > > could modify gcc to output one source/line combo on TOC entries, but > > we don't do that currently. > > > > A similar situation happens on ppc32 with -fPIC and the .got2 section, > > which again is a compiler managed GOT. > > It sounds like it's impractical, then, to get a line number in this > case, so I'd suggest suppressing that one check for powerpc. > > Something like the attached should work. Thanks! It does, and I'm happy with it from a powerpc testing perspective. -- Alan Modra Australia Development Lab, IBM
- Previous message (by thread): [GOLD] debug_msg test
- Next message (by thread): [GOLD] debug_msg test
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list