https://github.com/DavidSpickett commented:
I don't want a fix for AArch64 TLS to break TLS support elsewhere, so this needs testing and we may need to add new tests for the existing support. Could you: * Find out what TLS testing we have right now. (a really ugly way to do it is to delete the TLS handling code and see what fails) * If it doesn't cover what you're modifying, extend that and PR those changes. * Write a test case for this new code, which will: * Include the situation Pavel brought up. * Include the limitation around static thread local * Include any other assumptions you're making. Another overall topic is, if we landed this then improved the compilers, would the new objects "just work" or would we need to remove this workaround? Which would then break debugging older binaries. (this is a tradeoff we can make if it's worth it, but also we could choose to improve the compilers right now instead) https://github.com/llvm/llvm-project/pull/110822 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
