public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yshuiv7 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94391] gcc refers to absolute symbols with R_X86_64_PC32 relocation
Date: Mon, 30 Mar 2020 09:29:26 +0000	[thread overview]
Message-ID: <bug-94391-4-QnFJuXTpWx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94391-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94391

--- Comment #11 from Yuxuan Shui <yshuiv7 at gmail dot com> ---
(In reply to Andrew Pinski from comment #8)
> Also it is wrong for a person to assume a normal C variable could be
> SHN_ABS; that is the bug here.  It is a bug in the user code.
> I showed up to fix it by using an top level inline-asm.

Why is this wrong? Is it written down somewhere that a C variable can never be
SHN_ABS, perhaps in the standard, or in the X86-psABI?

If this is wrong, then what is the correct way to access a SHN_ABS symbol? Is
it just no way to do it? If so, what's the purpose of objcopy generating such
symbols?

  parent reply	other threads:[~2020-03-30  9:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 21:05 [Bug other/94391] New: " yshuiv7 at gmail dot com
2020-03-29 21:17 ` [Bug target/94391] " pinskia at gcc dot gnu.org
2020-03-29 23:34 ` yshuiv7 at gmail dot com
2020-03-29 23:37 ` pinskia at gcc dot gnu.org
2020-03-29 23:51 ` hjl.tools at gmail dot com
2020-03-30  2:40 ` i at maskray dot me
2020-03-30  2:42 ` i at maskray dot me
2020-03-30  2:45 ` pinskia at gcc dot gnu.org
2020-03-30  2:46 ` pinskia at gcc dot gnu.org
2020-03-30  3:48 ` hjl.tools at gmail dot com
2020-03-30  4:14 ` i at maskray dot me
2020-03-30  9:29 ` yshuiv7 at gmail dot com [this message]
2020-03-30 11:01 ` hjl.tools at gmail dot com
2020-03-30 12:22 ` hjl.tools at gmail dot com
2020-03-30 12:42 ` hjl.tools at gmail dot com
2020-03-30 16:14 ` yshuiv7 at gmail dot com
2020-03-30 20:15 ` hjl.tools at gmail dot com
2020-03-30 23:27 ` yshuiv7 at gmail dot com
2020-03-30 23:31 ` pinskia at gcc dot gnu.org
2020-03-30 23:33 ` yshuiv7 at gmail dot com
2020-03-30 23:34 ` yshuiv7 at gmail dot com
2020-03-30 23:36 ` pinskia at gcc dot gnu.org
2020-03-30 23:39 ` yshuiv7 at gmail dot com
2020-03-31  1:26 ` 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-94391-4-QnFJuXTpWx@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).