DavidSpickett wrote: Just doing some googling, mostly people talk about modifying the binutils in the gnu toolchain for custom instructions and rebuilding it.
[This](https://www.ashling.com/wp-content/uploads/PR_CUSTOM_INST_17-FEB-2022.pdf) refers to some XML file, but I can't tell if they're talking about an upstream patch, or their own product based on GDB: > we have recently worked on a GDB patch to allow these custom instruction > mnemonics > to be defined in an XML file which GDB can read and use to display the > instruction (and parameters) in a > human-readable format. Might be my search skills, but I only see references to XML for target descriptions in upstream GDB. Anyway, that's another approach that I guess would require each tool to add an option to load that file. Rather than your proposal which wraps the filter around the tool (kind of, the custom command is still inside of lldb from the user's perspective). https://github.com/llvm/llvm-project/pull/145793 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
