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 rtl-optimization/100377] needless stack adjustment when passing struct in register
Date: Sat, 01 May 2021 20:59:19 +0000 [thread overview]
Message-ID: <bug-100377-4-cOP2e4zLjR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100377-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100377
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |94173, 90216
Severity|normal |enhancement
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Luc Van Oostenryck from comment #0)
>
> Note: similar PRs exist but reported for x86_64 only
Not true. PR 94173, PR 90216.
I thought there was one which I filed which is much older than those but I
can't find it.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90216
[Bug 90216] Stack Pointer decrementing even when not loading extra data to
stack.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94173
[Bug 94173] [RISCV] Superfluous stackpointer manipulation
next prev parent reply other threads:[~2021-05-01 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 19:20 [Bug rtl-optimization/100377] New: " luc.vanoostenryck at gmail dot com
2021-05-01 20:59 ` pinskia at gcc dot gnu.org [this message]
2021-05-01 21:00 ` [Bug rtl-optimization/100377] " pinskia at gcc dot gnu.org
2021-05-02 14:05 ` luc.vanoostenryck at gmail dot com
2021-05-03 8:02 ` rguenth 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-100377-4-cOP2e4zLjR@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).