public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108315] -mcpu=power10 changes ABI
Date: Tue, 28 Feb 2023 06:15:43 +0000	[thread overview]
Message-ID: <bug-108315-4-7qdB9jO4Yn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108315-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Alan implemented the special case of .localentry 1 in this patch for the BFD
linker (that appeared in binutils 2.32 if my calculations are correct):
https://sourceware.org/pipermail/binutils/2018-July/103936.html

and, I think, in this patchset for the Gold linker:
https://sourceware.org/pipermail/binutils/2019-July/107486.html

Corresponding support in the LLVM linker (LLD) also seems to appear around
2018.

It looks like de-facto ABI change even if on paper nothing changed, because all
Linux linkers interpreted .localentry 1 accordingly to the general rule and
would silently produce wrong code. Hence my suggestion to document it.

Plus, someone would have to reach out to the mold maintainer, as mold doesn't
seem to implement this special case.

  parent reply	other threads:[~2023-02-28  6:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 11:23 [Bug target/108315] New: " amonakov at gcc dot gnu.org
2023-02-28  2:57 ` [Bug target/108315] " bergner at gcc dot gnu.org
2023-02-28  5:07 ` linkw at gcc dot gnu.org
2023-02-28  6:15 ` amonakov at gcc dot gnu.org [this message]
2023-02-28  6:31 ` amonakov at gcc dot gnu.org
2023-02-28  8:05 ` amodra at gmail dot com
2023-02-28 15:33 ` marxin at gcc dot gnu.org
2023-02-28 16:01 ` segher at gcc dot gnu.org
2023-02-28 16:26 ` segher at gcc dot gnu.org
2023-03-01  1:24 ` rui314 at gmail dot com
2023-03-02 16:53 ` amonakov at gcc dot gnu.org
2023-03-03  1:06 ` rui314 at gmail dot com
2023-03-03  1:54 ` dje at gcc dot gnu.org
2023-03-03 17:30 ` segher at gcc dot gnu.org
2023-03-03 18:16 ` amonakov at gcc dot gnu.org
2023-03-03 19:31 ` segher at gcc dot gnu.org
2023-03-03 20:09 ` amonakov at gcc dot gnu.org
2023-03-03 21:45 ` segher at gcc dot gnu.org
2023-03-06 20:20 ` amonakov at gcc dot gnu.org
2023-10-12  4:09 ` bergner at gcc dot gnu.org
2023-10-12  4:34 ` rui314 at gmail dot com
2023-10-13  1:23 ` rui314 at gmail dot com

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-108315-4-7qdB9jO4Yn@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).