DavidSpickett wrote: > I'm not sure we can. The problem arises from transferring LLVM-IR values > to/from the targets memory. If we don't have the target consuming/producing > that memory then our test could just be consistently-wrong and pass anyway.
We can simulate a gdb-remote that's one of these unique architectures. It could check that the memory writes contain the right order of elements. Sometimes it's not possible because we have to mock too much stuff, but you can look at `lldb/test/API/functionalities/gdb_remote_client/TestXMLRegisterFlags.py` and `lldb/test/API/commands/expression/TestRegisterExpressionEndian.py` as examples. https://github.com/llvm/llvm-project/pull/155000 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
