[llvm-dev] How to force re-evaluate thread_local address?

[Rafael Espíndola via llvm-dev]

On 1 February 2016 at 14:13, Sean Silva via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> IIRC, this is a long-standing issue and some of our game teams that use
> coroutine-like job systems run into this as well. My recollection is that it
> is a big pile of work to fix this in the llvm backend. The workaround is to
> do all thread-local access via functions that access thread-local state and
> do not do any context-switching (and these functions must not be inlined,
> obviously).


Correct. This is pr19177.

Cheers,
Rafael