3D_iaYFtpR3d-2FR9fRvTiX3jMD42Aa63RX3G1cmVpk5p2CXwpUNZbHyoN4Gmkj0CQsf-2BpU8eoAlLy3BDguZ6b754B6goy0-2BfsekQgIIYApXSbULo2pu7lhczeHhjrTn3SbjloNRJi-2B2z8A-2Fw88cmCtoyhuiK04hFTj77MRILhZJS1xNsSHP9m4LqN6-2FWlGnKs45Ylt2RNsCq8wtl8f05gNbCBw-3D-3D
Feel free to let us know how we can be of further assistance.
Sincerely
Nancy GordonManager, Charter Divi
> It's not clear to my why you want this level of detail -- curiosity?
I need to enable this feature on open64.
Thank you all for your great infos.
--
Best Regards,
Yu Rong Tan
>> I can't find any code in cc1 or as that generate R_X86_64_DTPOFF32 in
>> .rela.debug_info section. Did I miss something?
>
> To expand on what Nathan said: the debug info needs to refer to the
> location of the variable 'i' somehow, and as it's a TLS variable that
> location is thread specific a
> .rela.X is a relocation section generated by the assembler. GCC emits debug
> information using assembler pseudos such as .word etc. Those will name
> relocations. The syntax for relocations is target-specific. The above will
> be some_symbol@dtpoff or something.
Sorry, I did not find it in
Dear list，
tls.c:
__thread int i=10;
$gcc -g -c -save-temps tls.c
$readelf -r tls.o
Relocation section '.rela.debug_info' at offset 0x2d0 contains 6 entries:
Offset Info Type Sym. ValueSym. Name + Addend
0006 0007000a R_X86_64_32 0
