public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110634] Incorrect RISC-V assembly with -fno-omit-frame-pointer Date: Tue, 11 Jul 2023 19:47:27 +0000 [thread overview] Message-ID: <bug-110634-4-ypI0hgIMVz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110634-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110634 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |WAITING Last reconfirmed| |2023-07-11 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I don't see where in any of the spec mentioned that storing of ra is needed at all. That is it does not read ambigous to me at all. It just mentions for a frame pointer, the frame pointer needs to be saved and nothing about ra. This is totally different from the power ABI.
next prev parent reply other threads:[~2023-07-11 19:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-11 19:43 [Bug c/110634] New: " bjorn at kernel dot org 2023-07-11 19:47 ` pinskia at gcc dot gnu.org [this message] 2023-07-11 19:50 ` [Bug target/110634] " bjorn at kernel dot org 2023-07-11 19:52 ` pinskia at gcc dot gnu.org 2023-07-11 20:07 ` schwab@linux-m68k.org 2023-07-19 17:57 ` cleger at rivosinc 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-110634-4-ypI0hgIMVz@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: linkBe 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).