search for: global_tls_address

...ctly access > TLS variables. I.e. on x86, it is effectively a statically allocated TLS > variable with fixed offset. That can be accessed by a single load -- > whereas introducing get_tcb_address first would require a second load. Guess I used the wrong intrinsic name - it should be llvm.global_tls_address(), and it should be directly lowered to ISD::GlobalTLSAddress, which is currently used by both x86 and ppc, and ultimately it's referencing fs register on x86_64 and r13 on ppc64le. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/piperma...

When -fstack-protector is turned on, linker fails to find the symbol "__stack_chk_guard" because at least for powerpc64le, glibc doesn't provide this symbol. Instead, they put the stack guard into TCB. x86 fixed this issue by injecting a special address space (which is later translated to TCB register access) and hard code the offset of stack_guard, but I don't see a easy way to