Re: [patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling

2011-10-18 Thread Tristan Gingold
On Oct 17, 2011, at 3:16 PM, Tom Tromey wrote: >> "Tristan" == Tristan Gingold writes: > > Tom> Another way to look at it is that there have been many changes to GCC's > Tom> DWARF output in the last few years. Surely these have broken these > Tom> DWARF consumers more than this change pos

Re: [patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling

2011-10-17 Thread Tom Tromey
> "Tristan" == Tristan Gingold writes: Tom> Another way to look at it is that there have been many changes to GCC's Tom> DWARF output in the last few years. Surely these have broken these Tom> DWARF consumers more than this change possibly could. Tristan> Yes, but there is -gstrict-dwarf to

Re: [patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling

2011-10-17 Thread Tristan Gingold
On Oct 14, 2011, at 4:02 PM, Tom Tromey wrote: >> "Tristan" == Tristan Gingold writes: > > Tristan> I am not against this patch, my only concern is that there are many > Tristan> many dwarf consumers and I have no idea how they will react to this > Tristan> change. > > I tend to think that

Re: [patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling

2011-10-14 Thread Tom Tromey
> "Tristan" == Tristan Gingold writes: Tristan> I am not against this patch, my only concern is that there are many Tristan> many dwarf consumers and I have no idea how they will react to this Tristan> change. I tend to think that this is the wrong standard to apply. In this case we would b

Re: [patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling

2011-10-14 Thread Tristan Gingold
On Oct 13, 2011, at 10:40 PM, Jan Kratochvil wrote: > On Wed, 12 Oct 2011 16:18:07 +0200, Jan Kratochvil wrote: >> On Wed, 12 Oct 2011 16:07:24 +0200, Tristan Gingold wrote: >>> I fear that this may degrade performance of other debuggers. What about >>> adding a command line option ? >> >> I ca

Re: [patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling

2011-10-13 Thread Jan Kratochvil
On Wed, 12 Oct 2011 16:18:07 +0200, Jan Kratochvil wrote: > On Wed, 12 Oct 2011 16:07:24 +0200, Tristan Gingold wrote: > > I fear that this may degrade performance of other debuggers. What about > > adding a command line option ? > > I can test idb, I do not find the difference measurable. Drop

Re: [patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling

2011-10-12 Thread Jan Kratochvil
On Wed, 12 Oct 2011 16:07:24 +0200, Tristan Gingold wrote: > I fear that this may degrade performance of other debuggers. What about > adding a command line option ? I can test idb, there aren't so many DWARF debuggers out there I think. If the default is removed DW_AT_sibling a new options may

Re: [patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling

2011-10-12 Thread Tristan Gingold
On Oct 12, 2011, at 3:50 PM, Jan Kratochvil wrote: > Hi, > > dropping the optional DWARF attribute DW_AT_sibling has only advantages and no > disadvantages: > > For files with .gdb_index GDB initial scan does not use DW_AT_sibling at all. > For files without .gdb_index GDB initial scan has 1.79

[patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling

2011-10-12 Thread Jan Kratochvil
Hi, dropping the optional DWARF attribute DW_AT_sibling has only advantages and no disadvantages: For files with .gdb_index GDB initial scan does not use DW_AT_sibling at all. For files without .gdb_index GDB initial scan has 1.79% time _improvement_. For .debug files it brings 3.49% size decreas