public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luofengwc at qq dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31302] glibc issue about reloc-type R_X86_64_TPOFF64 when llvm build golang project with cgo Date: Mon, 29 Jan 2024 11:41:11 +0000 [thread overview] Message-ID: <bug-31302-131-zJsFZOYsfO@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31302-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31302 --- Comment #9 from luofeng14 <luofengwc at qq dot com> --- this is glibc main function, the function init_static_tls is after the _dl_try_allocate_static_tls, this results in CHECK_STATIC_TLS failure,because dl_tls_static_size not initialled yet: LIBC_START_MAIN _dl_relocate_static_pie (); ELF_DYNAMIC_RELOCATE - ELF_DYNAMIC_DO_REL - _ELF_DYNAMIC_DO_RELOC - elf_dynamic_do_reloc # elf_dynamic_do_##reloc - elf_dynamic_do_Rela - elf_dynamic_do_Rel - elf_machine_rel - elf_machine_rela case R_X86_64_TPOFF64: CHECK_STATIC_TLS _dl_allocate_static_tls _dl_try_allocate_static_tls /* Perform IREL{,A} relocations. */ ARCH_SETUP_IREL (); /* The stack guard goes into the TCB, so initialize it early. */ ARCH_SETUP_TLS (); x86_setup_tls # define ARCH_SETUP_TLS() x86_setup_tls __libc_setup_tls init_static_tls -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-29 11:41 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-28 0:45 [Bug libc/31302] New: glibc issue about reloc-type R_X86_64_TPOFF64 when llvm build golang project with cgo, luofengwc at qq dot com 2024-01-28 0:48 ` [Bug libc/31302] glibc issue about reloc-type R_X86_64_TPOFF64 when llvm build golang project with cgo luofengwc at qq dot com 2024-01-28 0:51 ` luofengwc at qq dot com 2024-01-28 1:23 ` luofengwc at qq dot com 2024-01-28 8:32 ` sam at gentoo dot org 2024-01-28 19:30 ` fweimer at redhat dot com 2024-01-29 1:16 ` luofengwc at qq dot com 2024-01-29 1:23 ` luofengwc at qq dot com 2024-01-29 1:33 ` luofengwc at qq dot com 2024-01-29 1:39 ` luofengwc at qq dot com 2024-01-29 5:50 ` fweimer at redhat dot com 2024-01-29 11:41 ` luofengwc at qq dot com [this message] 2024-01-29 11:43 ` fweimer at redhat dot com 2024-01-30 1:05 ` luofengwc at qq dot com 2024-03-15 21:04 ` i at maskray dot me
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31302-131-zJsFZOYsfO@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).