A target description must contain either no registers or all the target’s registers. If the description contains no registers, then GDB will assume a default register layout, selected based on the architecture. If the description contains any registers, the default layout will not be used; the standard registers must be described in the target description, in such a way that GDB can recognize them.
This is accomplished by giving specific names to feature elements which contain standard registers. GDB will look for features with those names and verify that they contain the expected registers; if any known feature is missing required registers, or if any required feature is missing, GDB will reject the target description. You can add additional registers to any of the standard features — GDB will display them just as if they were added to an unrecognized feature.
This section lists the known features and their expected contents. Sample XML documents for these features are included in the GDB source tree, in the directory gdb/features.
Names recognized by GDB should include the name of the company or organization which selected the name, and the overall architecture to which the feature applies; so e.g. the feature containing ARM core registers is named ‘org.gnu.gdb.arm.core’.
The names of registers are not case sensitive for the purpose of recognizing standard features, but GDB will only display registers using the capitalization used in the description.
|• AArch64 Features:|
|• ARM Features:|
|• i386 Features:|
|• MicroBlaze Features:|
|• MIPS Features:|
|• M68K Features:|
|• Nios II Features:|
|• PowerPC Features:|
|• S/390 and System z Features:|
|• TIC6x Features:|