DavidSpickett wrote: > Upstream replaced LLDB_TEST_ARCH with LLDB_TEST_TRIPLE as the standard way to > way to define the test target. While this works for most cases, it is not sufficient for some dowsnstream use cases that require targeting a specific architecture configuration(e.g v1, v2 ... etc).
Can you provide a specific example of this because there are many ways to target a variant. Some of those go in the triple, a subset of those do go in the first component, but others don't and further flags might be `-march` `-m32` `-msoft-float` or that sort of thing. If the variant you want to target can be described as a triple, then change the triple. If it cannot, then replacing the arch component of a triple isn't going to help you. I want to be sure that: 1. What you propose actually works for your cases, and - 2. Isn't a far too specific version of a more general solution. https://github.com/llvm/llvm-project/pull/203211 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
