public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109456] `-ffixed` is ignored for `a` registers on RISC-V.
Date: Mon, 10 Apr 2023 11:42:27 +0000	[thread overview]
Message-ID: <bug-109456-4-rvjzDtrXEg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109456-4@http.gcc.gnu.org/bugzilla/>

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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #5 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Is this a bug?

-ffixed-reg
Treat the register named reg as a fixed register; generated code should never
refer to it (except perhaps as a stack pointer, frame pointer or in some other
fixed role).

To me "the ABI mandates to pass an argument in this register" means "some other
fixed role".

  parent reply	other threads:[~2023-04-10 11:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-09 15:25 [Bug c/109456] New: " gccriscvuser at proton dot me
2023-04-09 15:33 ` [Bug c/109456] " gccriscvuser at proton dot me
2023-04-09 15:37 ` [Bug middle-end/109456] " pinskia at gcc dot gnu.org
2023-04-09 15:43 ` pinskia at gcc dot gnu.org
2023-04-09 15:45 ` [Bug target/109456] " pinskia at gcc dot gnu.org
2023-04-10 11:42 ` xry111 at gcc dot gnu.org [this message]
2023-05-01 18:23 ` gccriscvuser at proton dot me
2023-05-01 20:19 ` gccriscvuser at proton dot me
2023-06-09 17:12 ` gccriscvuser at proton dot me
2023-06-11 10:23 ` xry111 at gcc dot gnu.org
2023-06-11 10:32 ` schwab@linux-m68k.org
2023-06-12  9:08 ` [Bug target/109456] `-ffixed-reg` cannot prevent using `reg` for ABI-mandated roles (argument register etc) and the behavior should be documented more clearly xry111 at gcc dot gnu.org
2023-06-23 17:39 ` gccriscvuser at proton dot me
2023-06-24  9:50 ` xry111 at gcc dot gnu.org
2023-06-24 10:04 ` xry111 at gcc dot gnu.org

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-109456-4-rvjzDtrXEg@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).