mchoo7 wrote: > I see the principle of it, but I am not sure what this is in aid of. >
Register-related files in Process/Utility are hard to read so I want to refactor them under lldbRegister (source/Register) by arch/OS. If you don't like creating new register library, I can just refactor under Process/Utility. But I think putting them into a separate library prevents developers from making similar mistakes in future (e.g. mixing register definitions and platform-specific interface). > Also, is this PR a half step to this being a "proper" library? Because it's > currently nested within utility, and it seems like it shouldn't be. Yes. https://github.com/llvm/llvm-project/pull/222330 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
