* doc/invoke.texi: Document -gdwarf{,-2} vs debug level.

From-SVN: r52770
This commit is contained in:
Richard Henderson 2002-04-25 15:33:21 -07:00 committed by Richard Henderson
parent cc03dff663
commit adc6b5fd82
2 changed files with 9 additions and 2 deletions

View File

@ -1,3 +1,7 @@
2002-04-25 Richard Henderson <rth@redhat.com>
* doc/invoke.texi: Document -gdwarf{,-2} vs debug level.
2002-04-25 Ulrich Weigand <uweigand@de.ibm.com>
* config/s390/s390.c (s390_emit_epilogue): Always restore registers

View File

@ -2796,8 +2796,6 @@ supported). This is the format used by DEBUG on VMS systems.
@itemx -gstabs@var{level}
@itemx -gcoff@var{level}
@itemx -gxcoff@var{level}
@itemx -gdwarf@var{level}
@itemx -gdwarf-2@var{level}
@itemx -gvms@var{level}
Request debugging information and also use @var{level} to specify how
much information. The default level is 2.
@ -2811,6 +2809,11 @@ Level 3 includes extra information, such as all the macro definitions
present in the program. Some debuggers support macro expansion when
you use @option{-g3}.
Note that in order to avoid confusion between DWARF1 debug level 2,
and DWARF2, neither @option{-gdwarf} nor @option{-gdwarf-2} accept
a concatenated debug level. Instead use an additional @option{-g@var{level}}
option to change the debug level for DWARF1 or DWARF2.
@cindex @code{prof}
@item -p
@opindex p