forked from Imagelibrary/binutils-gdb
8bfd04ec61
Some gdbserver targets generate their target description based on the gdb/regformats/*.dat files. These .dat files are generated from a matching xml file in gdb/features/. Lets consider a concrete example: Take gdb/features/or1k-linux.xml, this file is processed by gdb/features/Makefile to create gdb/regformats/or1k-linux.dat. When gdbserver is built for the or1k target the file or1k-linux-generated.cc is generated using the gdb/regformats/regdat.sh script. This .cc file is then compiled and linked into gdbserver. The or1k-linux-generated.cc file contains the function init_registers_or1k_linux which is called from within gdbserver, this function creates a target_desc object and sets its xmltarget field to a fixed string. This fixed string is the xml filename that was originally used to generate the xml file, in this case or1k-linux.xml. Additionally, as part of the gdbserver build the file or1k-linux.xml is converted to a string and placed in the file xml-builtin-generated.cc which is then built into gdbserver. Now when GDB asks gdbserver for the target description, gdbserver returns the fixed xmltarget string, which is the name of an xml file. GDB will then ask gdbserver for that file and gdbserver will return the contents of that file thanks to the xml-builtin-generated.cc file's contents. This is all rather complicated, but it does work. So what's the problem that I'm fixing? Well or1k-linux.xml does contain the osabi information, so this will be returned from gdbserver to GDB. That's good. However, the target_desc object created in init_registers_or1k_linux will not have its osabi set correctly. Now this doesn't really matter too much except init_registers_or1k_linux includes a call to init_target_desc. In the next commit I want to extend init_target_desc to require an osabi to be passed in. The motivation for this will be explained in the next commit, but if we accept for a moment that this is something that should be done, then the question is what osabi should we use in init_registers_or1k_linux? Ideally we'd use the osabi which is set in or1k-linux.xml. If we do that then everything will remain consistent, which is a good thing. And so, to get the osabi from or1k-linux.xml into init_registers_or1k_linux, we first need to get the osabi information into or1k-linux.dat file, and this is what this commit does. I've added a new xsl script print-osabi.xsl and updated gdb/features/Makefile to make use of this script. Then I regenerated all of the .dat files. Now every .dat file contains either: osabi:GNU/Linux osabi:unknown The first is for xml files containing <osabi>GNU/Linux</osabi> and the second is for xml files that don't contain an osabi element. This commit doesn't attempt to make use of the osabi information in the .dat files, that will come in the next commit. There should be no user visible changes after this commit.
80 lines
682 B
Plaintext
80 lines
682 B
Plaintext
# THIS FILE IS GENERATED. -*- buffer-read-only: t -*- vi :set ro:
|
|
# Generated from: mips64-linux.xml
|
|
name:mips64_linux
|
|
xmltarget:mips64-linux.xml
|
|
expedite:r29,pc
|
|
osabi:GNU/Linux
|
|
64:r0
|
|
64:r1
|
|
64:r2
|
|
64:r3
|
|
64:r4
|
|
64:r5
|
|
64:r6
|
|
64:r7
|
|
64:r8
|
|
64:r9
|
|
64:r10
|
|
64:r11
|
|
64:r12
|
|
64:r13
|
|
64:r14
|
|
64:r15
|
|
64:r16
|
|
64:r17
|
|
64:r18
|
|
64:r19
|
|
64:r20
|
|
64:r21
|
|
64:r22
|
|
64:r23
|
|
64:r24
|
|
64:r25
|
|
64:r26
|
|
64:r27
|
|
64:r28
|
|
64:r29
|
|
64:r30
|
|
64:r31
|
|
64:status
|
|
64:lo
|
|
64:hi
|
|
64:badvaddr
|
|
64:cause
|
|
64:pc
|
|
64:f0
|
|
64:f1
|
|
64:f2
|
|
64:f3
|
|
64:f4
|
|
64:f5
|
|
64:f6
|
|
64:f7
|
|
64:f8
|
|
64:f9
|
|
64:f10
|
|
64:f11
|
|
64:f12
|
|
64:f13
|
|
64:f14
|
|
64:f15
|
|
64:f16
|
|
64:f17
|
|
64:f18
|
|
64:f19
|
|
64:f20
|
|
64:f21
|
|
64:f22
|
|
64:f23
|
|
64:f24
|
|
64:f25
|
|
64:f26
|
|
64:f27
|
|
64:f28
|
|
64:f29
|
|
64:f30
|
|
64:f31
|
|
64:fcsr
|
|
64:fir
|
|
64:restart
|