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: Tue, 30 Jan 2024 01:05:56 +0000 [thread overview]
Message-ID: <bug-31302-131-muagyyYGyI@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 #11 from luofeng14 <luofengwc at qq dot com> ---
(In reply to Florian Weimer from comment #10)
> There should not be any R_X86_64_TPOFF64 relocations left in static PIE
> because the link editor can fully resolve them. This is an lld bug.
sorry, i'm not familiar with relocation type. i would like to ask in which case
R_X86_64_TPOFF64 relocation type would be used.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-30 1:05 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
2024-01-29 11:43 ` fweimer at redhat dot com
2024-01-30 1:05 ` luofengwc at qq dot com [this message]
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-muagyyYGyI@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: link
Be 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).