public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kito at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106338] RISC-V static-chain register may be clobbered by PLT stubs
Date: Wed, 10 Aug 2022 02:58:09 +0000	[thread overview]
Message-ID: <bug-106338-4-sW0gb6sOeY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106338-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Kito Cheng <kito at gcc dot gnu.org> ---
My understanding is static chain is sort of compiler internal implementation,
any register could be picked if that is not used for passing argument, so I
would also prefer keep that out psABI spec for now.


And just record info for myself:

x86-64 ABI has document function's static chain pointer in their ABI

https://gitlab.com/x86-psABIs/x86-64-ABI/-/blob/master/x86-64-ABI/low-level-sys-info.tex#L701

      parent reply	other threads:[~2022-08-10  2:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  8:00 [Bug target/106338] New: " funanzeng at gmail dot com
2022-07-18  8:12 ` [Bug target/106338] " pinskia at gcc dot gnu.org
2022-07-18  8:13 ` pinskia at gcc dot gnu.org
2022-07-18  8:17 ` schwab@linux-m68k.org
2022-08-09 19:47 ` pinskia at gcc dot gnu.org
2022-08-09 21:11 ` andrew at sifive dot com
2022-08-10  2:58 ` kito at gcc dot gnu.org [this message]

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-106338-4-sW0gb6sOeY@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).