Lines Matching refs:pointer

24 architecture-specific thread pointer (TP) and can be accessed very efficiently -- typically just a
31 architecture-specific thread-pointer ([`__get_tls()`] in Bionic):
44 Each thread has a "Dynamic Thread Vector" (DTV) with a pointer to each module's TLS block (or NULL
47 expected to point immediately at the DTV pointer, whereas in variant 2, the DTV pointer's offset
176 // TPOFF is directly relative to the thread pointer.
379 thread pointer (e.g. `ps_get_thread_area`).
391 pointer was removed in [D10661] ([this function][r240543]). (arm32 was apparently never supported.)
416 `_thread_db_pthread_dtvp`         | Offset from TP to DTV pointer (0 for variant 1, implementation-…
418 `_thread_db_dtv_t_pointer_val`    | Offset within a DTV slot to the pointer to the allocated TLS bl…
427  * Read the target thread pointer.
431  * Add the module-relative offset to the module pointer.
440 There are ptrace interfaces for reading the thread pointer for each of arm32, arm64, x86, and x86-64
532 the prototype uses a [special function pointer] to call libc.so's `__tls_get_addr` from the loader.
540 [special function pointer]: https://android-review.googlesource.com/c/platform/bionic/+/723698/1/li…
621       the thread pointer looking for it. [The scan count was bumped to 384 to fix a reported
625     * On x86/x86-64, it uses a fixed offset from the thread pointer (TP+0xf8 or TP+0x1d0) and
632     * Moving the pthread keys before the thread pointer breaks Go-based apps.
829 Go scans 384 words from the thread pointer. If there are at most 16 Bionic slots and 130 pthread
833 that pthread keys are at a fixed offset from the thread pointer anymore. It must load an offset from