Using and Porting the GNU Compiler Collection (GCC)
These macros affect all debugging formats.
DBX_REGISTER_NUMBER (regno)
If two registers have consecutive numbers inside GNU CC, and they can be
used as a pair to hold a multiword value, then they must have
consecutive numbers after renumbering with DBX_REGISTER_NUMBER.
Otherwise, debuggers will be unable to access such a pair, because they
expect register pairs to be consecutive in their own numbering scheme.
If you find yourself defining DBX_REGISTER_NUMBER in way that
does not preserve register pairs, then what you must do instead is
redefine the actual register numbering scheme.
DEBUGGER_AUTO_OFFSET (x)
-g' options is used.
DEBUGGER_ARG_OFFSET (offset, x)
PREFERRED_DEBUGGING_TYPE
-g'. Define
this if you have arranged for GNU CC to support more than one format of
debugging output. Currently, the allowable values are DBX_DEBUG,
SDB_DEBUG, DWARF_DEBUG, DWARF2_DEBUG, and
XCOFF_DEBUG.
When the user specifies `-ggdb', GNU CC normally also uses the
value of this macro to select the debugging output format, but with two
exceptions. If DWARF2_DEBUGGING_INFO is defined and
LINKER_DOES_NOT_WORK_WITH_DWARF2 is not defined, GNU CC uses the
value DWARF2_DEBUG. Otherwise, if DBX_DEBUGGING_INFO is
defined, GNU CC uses DBX_DEBUG.
The value of this macro only affects the default debugging output; the
user can always get a specific type of output by using `-gstabs',
`-gcoff', `-gdwarf-1', `-gdwarf-2', or `-gxcoff'.
Using and Porting the GNU Compiler Collection (GCC)
Packaging copyright © 1988-2000 OAR Corporation Context copyright by each document's author. See Free Software Foundation for information.