F.2.5 Registers

Each register is represented as an element with this form:

<reg name="name"
     bitsize="size"
     [regnum="num"]
     [save-restore="save-restore"]
     [type="type"]
     [group="group"]/>

The components are as follows:

name

The register's name; it must be unique within the target description.

bitsize

The register's size, in bits.

regnum

The register's number. If omitted, a register's number is one greater than that of the previous register (either in the current feature or in a preceeding feature); the first register in the target description defaults to zero. This register number is used to read or write the register; e.g. it is used in the remote p and P packets, and registers appear in the g and G packets in order of increasing register number.

save-restore

Whether the register should be preserved across inferior function calls; this must be either yes or no. The default is yes, which is appropriate for most registers except for some system control registers; this is not related to the target's ABI.

type

The type of the register. type may be a predefined type, a type defined in the current feature, or one of the special types int and float. int is an integer type of the correct size for bitsize, and float is a floating point type (in the architecture's normal floating point format) of the correct size for bitsize. The default is int.

group

The register group to which this register belongs. group must be either general, float, or vector. If no group is specified, No value for GDBN will not display the register in info registers.