Jason Molenda 1659276bee Support nested target.xml register definition files, lack of reg group markers. ... The qemu x86_64 target returns a target.xml register definition file which includes other xml files and they include others, etc. Also, the registers are not put in register groups like lldb wants to see. This patch (1) puts registers that aren't in a register group in a "general" register group, (2) change ProcessGDBRemote::GetGDBServerRegisterInfo to be a method that starts the parsing, asking a recurisve function to fetch and parse target.xml, (3) adds ProcessGDBRemote::GetGDBServerRegisterInfoXMLAndProcess which can recusively call itself to read and parse included xml files, (4) in addition to expecting the top-level <target> element (which only happens in the top level xml file), also an xml file that consists of a <feature> node - read the register defintions and includes from that <feature> element. <rdar://problem/49537922> Differential revision: https://reviews.llvm.org/D63802 llvm-svn: 364484		2019-06-26 21:59:39 +00:00
..
pre_kill_hook
support	[testsuite] Drop characters that can't be decoded, restoring parity with Py2.	2019-03-07 17:45:53 +00:00
test	Support nested target.xml register definition files, lack of reg group markers.	2019-06-26 21:59:39 +00:00
test_event	Update the file headers across all of the LLVM projects in the monorepo	2019-01-19 08:50:56 +00:00
__init__.py
.clang-format