public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Richard Sandiford <Richard.Sandiford@arm.com>
Cc: Wilco Dijkstra via Gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] AArch64: Cleanup aarch64_classify_symbol
Date: Fri, 30 Apr 2021 12:11:36 +0000	[thread overview]
Message-ID: <VE1PR08MB5599A76E0843509011836951835E9@VE1PR08MB5599.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <mptr1is9n3o.fsf@arm.com>

Hi Richard,

> Hmm, OK.  I guess it makes things more consistent in that sense
> (PIC vs. non-PIC).  But on the other side it's making things less
> internally consistent for non-PIC, since we don't use the GOT for
> anything else there.  I guess in principle there's a danger that a
> custom *-elf linker script might not bother to set up the .got properly,
> on the assumption that it shouldn't be needed.

The GOT is always used in executables (even an empty main function has
a non-zero .got and .got.plt section). When you need an indirection,
using an existing mechanism is better than doing something special.
For example if the weak reference is resolved to a local symbol, the
linker could remove the indirection.

Cheers,
Wilco

  reply	other threads:[~2021-04-30 12:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 14:36 Wilco Dijkstra
2021-04-28 15:34 ` Richard Sandiford
2021-04-28 17:48   ` Wilco Dijkstra
2021-04-30  8:46     ` Richard Sandiford
2021-04-30 12:11       ` Wilco Dijkstra [this message]
2021-04-30 12:50         ` Richard Sandiford
2021-04-28 18:04 ` Andrew Pinski
2021-04-28 20:34   ` Wilco Dijkstra

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=VE1PR08MB5599A76E0843509011836951835E9@VE1PR08MB5599.eurprd08.prod.outlook.com \
    --to=wilco.dijkstra@arm.com \
    --cc=Richard.Sandiford@arm.com \
    --cc=gcc-patches@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).