Re: Making CFLAGS=-g1 bigger but more useful

2009-04-25 Thread Ian Lance Taylor
Andi Kleen writes: >> It's not quite that, but the gold linker has a --strip-debug-non-line >> option which discards all the debugging information except what is >> needed to map addresses to lines. > > The reason I would like to have it is that generating so much data > slows down gcc compilatio

Re: Making CFLAGS=-g1 bigger but more useful

2009-04-25 Thread Andi Kleen
On Sat, Apr 25, 2009 at 10:30:51AM -0700, Ian Lance Taylor wrote: > Andi Kleen writes: > > > On Fri, Apr 24, 2009 at 08:24:56PM -0400, Frank Ch. Eigler wrote: > >> > >> I'm working on a little patch that extends the data produced for the > >> little-used (?) -g1 mode. Normally, this produces v

Re: Making CFLAGS=-g1 bigger but more useful

2009-04-25 Thread Ian Lance Taylor
Andi Kleen writes: > On Fri, Apr 24, 2009 at 08:24:56PM -0400, Frank Ch. Eigler wrote: >> >> I'm working on a little patch that extends the data produced for the >> little-used (?) -g1 mode. Normally, this produces very little DWARF >> data (basically just function declaration locus, PC range,

Re: Making CFLAGS=-g1 bigger but more useful

2009-04-25 Thread Andi Kleen
> Another possibility, though a much bigger amount of work, would be to > introduce -g options like -f. The presence of such an option would > imply -g1 or higher, and then you could add -gparameters, > -gline-numbers, -gvar-tracking, -gmacros, etc. I would like to have that. -Andi -- a...@linu

Re: Making CFLAGS=-g1 bigger but more useful

2009-04-25 Thread Paolo Bonzini
> The basic question though is whether there is interest here for this > sort of -g1.5 mode. We could ... Yes, definitely. I thought about it in two contexts -- regular debugging, and the fact that the OpenCL GSOC project might require looking at debug info for memory spaces and types of argumen

Re: Making CFLAGS=-g1 bigger but more useful

2009-04-25 Thread Andi Kleen
On Fri, Apr 24, 2009 at 08:24:56PM -0400, Frank Ch. Eigler wrote: > > I'm working on a little patch that extends the data produced for the > little-used (?) -g1 mode. Normally, this produces very little DWARF > data (basically just function declaration locus, PC range, and basic > backtrace-enab

Making CFLAGS=-g1 bigger but more useful

2009-04-24 Thread Frank Ch. Eigler
Hi - I'm working on a little patch that extends the data produced for the little-used (?) -g1 mode. Normally, this produces very little DWARF data (basically just function declaration locus, PC range, and basic backtrace-enabling data). Compared to normal -g (== -g2) mode, this is very small.