llvm-project/lldb/source/Plugins/Architecture/CMakeLists.txt

add_subdirectory(Arm)
add_subdirectory(Mips)
add_subdirectory(PPC64)
add_subdirectory(AArch64)
Move StopInfoOverride callback to the new architecture plugin This creates a new Architecture plugin and moves the stop info override callback to this place. The motivation for this is to remove complex dependencies from the ArchSpec class because it is used in a lot of places that (should) know nothing about Process instances and StopInfo objects. I also add a test for the functionality covered by the override callback. Differential Revision: https://reviews.llvm.org/D31172 llvm-svn: 316609 2017-10-25 21:05:31 +00:00			`add_subdirectory(Arm)`
Move architecture-specific address adjustment to architecture plugins Differential Revision: https://reviews.llvm.org/D48623 llvm-svn: 342762 2018-09-21 18:56:44 +00:00			`add_subdirectory(Mips)`
Re-add change for https://reviews.llvm.org/D42582 with added directories. llvm-svn: 327331 2018-03-12 21:17:04 +00:00			`add_subdirectory(PPC64)`
[lldb][AArch64] Add MTE memory tag reading to lldb This adds GDB client support for the qMemTags packet which reads memory tags. Following the design which was recently committed to GDB. https://sourceware.org/gdb/current/onlinedocs/gdb/General-Query-Packets.html#General-Query-Packets (look for qMemTags) lldb commands will use the new Process methods GetMemoryTagManager and ReadMemoryTags. The former takes a range and checks that: * The current process architecture has an architecture plugin * That plugin provides a MemoryTagManager * That the range of memory requested lies in a tagged range (it will expand it to granules for you) If all that was true you get a MemoryTagManager you can give to ReadMemoryTags. This two step process is done to allow commands to get the tag manager without having to read tags as well. For example you might just want to remove a logical tag, or error early if a range with tagged addresses is inverted. Note that getting a MemoryTagManager doesn't mean that the process or a specific memory range is tagged. Those are seperate checks. Having a tag manager just means this architecture could have a tagging feature enabled. An architecture plugin has been added for AArch64 which will return a MemoryTagManagerAArch64MTE, which was added in a previous patch. Reviewed By: omjavaid Differential Revision: https://reviews.llvm.org/D95602 2021-02-19 15:57:29 +00:00			`add_subdirectory(AArch64)`