Lines Matching refs:x86

325    x86, x86-64).
352 x86             | yes | yes  | yes
361 x86 (experimental)    | yes | yes                | unsupported relocs
388 LLDB more-or-less implemented Linux TLS debugging in [r192922][rL192922] ([D1944]) for x86 and
389 x86-64. [arm64 support came later][D5073]. However, the Linux TLS functionality no longer does
440 There are ptrace interfaces for reading the thread pointer for each of arm32, arm64, x86, and x86-64
476  * On arm32, x86, and x86_64, the loader [should reject a TLS relocation]. (XXX: I haven't verified
610    by GCC on x86 (and x86-64), where it is compatible with x86's TLS variant 2. We [modified Clang
625     * On x86/x86-64, it uses a fixed offset from the thread pointer (TP+0xf8 or TP+0x1d0) and
630        * x86: https://go-review.googlesource.com/c/go/+/16678
631        * x86-64: https://go-review.googlesource.com/c/go/+/15991
635     * [On x86/x86-64 Darwin, Go uses a TLS slot reserved for both Go and Wine][go-darwin-x86] (On
640    example, it could be used to load an arm32 solib into an x86 Zygote.) The solib is translated
649 It seems easy to fix the incompatibility for variant 2 (x86 and x86_64) by splitting out the Bionic
663 [go-darwin-x86]: https://github.com/golang/go/issues/23617
763  * x86/x86-64 relocations probably handle positive offsets without issue
772  * Bionic's existing memory layout doesn't change, and arm32 and 32-bit x86 have the same layout
852 General (and x86/x86-64)
854    overall ELF TLS design and ABI details for x86 and x86-64 (as well as several other architectures
856  * Alexandre Oliva's TLSDESC proposal with details for x86 and x86-64: ["Thread-Local Storage
857    Descriptors for IA32 and AMD64/EM64T."][tlsdesc-x86]
858  * [x86 and x86-64 SystemV psABIs][psabi-x86].
875 [tlsdesc-x86]: https://www.fsfla.org/~lxoliva/writeups/TLS/RFC-TLSDESC-x86.txt
876 [psabi-x86]: https://github.com/hjl-tools/x86-psABI/wiki/X86-psABI