bgergely0 wrote: I fill make the description a bit more formal.
I agree that naming all the unittests a bit more similarly is good addition to this. One piece of doubt that I have since I opened this PR: the term CFI is overloaded, it can mean *Call Frame Information* and *Control Flow Integrity*. This is even more problematic than normal in this case, where we talk about the Call Frame Information related to a Control Flow Integrity mechanism, namely Pointer Authentication. Another way to name these would be PointerAuthDwarf* (or capital DWARF*), to signal that these passes take care of the *DWARF CFIs* in the binary. Thoughts? https://github.com/llvm/llvm-project/pull/164622 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
