Lines Matching refs:access

58 address using a TLS "access model". The access models trade generality against efficiency. The four
70 A GD access can refer to a TLS variable anywhere. To access a variable `tls_var` using the
187 part of the executable (and referenced from the executable), then a GOT access can be avoided. The
199 The compiler selects an access model for each variable reference using these factors:
289    need to use an atomic or synchronized access of the global TLS generation counter.
320 The static linker can still relax a TLSDESC-based access to an IE/LE access.
336 to IE or LE. To relax a TLS access, the linker looks for an expected sequences of instructions and
364 arm32 linkers can't relax traditional TLS accesses. BFD can relax an arm32 TLSDESC access, but LLD
422 dynamic symbol table). Debuggers can access them, but applications can't.
434 read past the end of an out-of-date DTV or access an unloaded module. To be robust, it needs to
464 each access, to call a function to initialize the variable.
554 out-of-memory error on a TLS access aborts the process. musl, on the other hand, preallocates TLS
602  ** linker and the OpenGL sub-system (which needs to access the
645  * A `pthread_t` is practically just a `pthread_internal_t*`, and some apps directly access the
655 Aside: gcc's arm64ilp32 target uses a 32-bit unsigned offset for a TLS IE access
782 shared object can still use the efficient IE access model, but its TLS segment offset is known at