[llvm] GlobalsModRef, ValueTracking: Look through threadlocal.address intrinsic (PR #88418)

[Matthias Braun via llvm-commits]

MatzeB wrote:

It's possible I missed most of the discussion around this intrinsic. To me this mostly felt like coroutines were breaking because the underlying thread could change across `yield` points?

At least for `GlobalsAAResult::AnalyzeUsesOfPointer` it shouldn't really matter at what thread we are looking at... I guess for `llvm::getUnderlyingObject` it could depend on what calling code is using it for whether changing threads are a problem... 

Either way for my use cases here the intrinsic is showing up as a code quality regression compared to older LLVM versions...

https://github.com/llvm/llvm-project/pull/88418