Re: Designs for better debug info in GCC. Choice A or B?

3 msg	gcc 4.2.2, libgomp under cygwin
4 msg	PR1634: Request for gcc-cvs-patches list
6 msg	Idea to refine -Wtype-limits
1 msg	Bounce Test
1 msg	[Fwd: Libiberty problem in gcc-4.3 snapshots]
7 msg	[RFC] [PATCH] 32-bit pointers in x86-64

Re: Designs for better debug info in GCC. Choic...
\ J.C. Pizarro (25 Nov 2007)
. \ J.C. Pizarro (25 Nov 2007)
. . \ Ye, Joey (26 Nov 2007)
. . . \ Robert Dewar (26 Nov 2007)
. . . . \ J.C. Pizarro (26 Nov 2007)
. \ J.C. Pizarro (25 Nov 2007)
. \ J.C. Pizarro (25 Nov 2007)
. \ J.C. Pizarro (26 Nov 2007)

4 msg	Autovectorizing HIRLAM; some progress.
3 msg	Infinite loop when trying to bootstrap trunk
1 msg	gcc-4.3-20071123 is now available
1 msg	Status of GCC 4.3 on IA64 (Debian)
5 msg	[Fwd: Re: FW: matrix linking]
8 msg	Does gcc support compiling for windows x86-64?
1 msg	RiW k sLG
7 msg	-Wconversion bug in g++-4.3?
5 msg	Simple way to write almost same pattern?
2 msg	unsatisfied link error
1 msg	gcc-4.2-20071121 is now available
2 msg	Status of GCC 4.3 on SPARC (Debian)
7 msg	Problem with ARM_DOUBLEWORD_ALIGN on ARM

Subject:	Re: Designs for better debug info in GCC. Choice A or B?
Group:	Gcc
From:	J.C. Pizarro
Date:	25 Nov 2007

To imagine that i'm using "-g -Os -finline-functions -funroll-loops".

There are differences in how to generate "optimized AND debugged" code.

A) Whole-optimized but with dirty debugged information if possible.
-------------------------------------------------------------------------------- ----
When there is coredump from crash then its debugged information can
be not complete (with losses) but can be readable for humans.
This kind of strategy can't work well in "step to step" debuggers like
gdb, ddd, kgdb, ... but its code is whole-optimized same as stripped program.

B) Whole-debugged but partially optimized because of restricted requirements
to maintain the full debugged information without losses.
-------------------------------------------------------------------------------- ----
This kind of strategy works well in "step to step" debuggers like
gdb, ddd, kgdb, ... but its code is less whole-optimized and bigger than
stripped program.

Sincerely, J.C.Pizarro