public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102758] [12 Regression] Failure to use registers optimally with return values (2 operands related and subreg)
Date: Fri, 03 Dec 2021 16:37:57 +0000	[thread overview]
Message-ID: <bug-102758-4-LbOqjZHtGq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102758-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> Richard?  How does the new fwprop behave wrt hardregs?
It doesn't sound like this is new vs. old fwprop, since new fwprop
was in GCC 11.  Generally the idea was to follow the existing
behaviour as closely as possible, so I don't know of any specific
differences re: hard regs.

  parent reply	other threads:[~2021-12-03 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  2:24 [Bug target/102758] New: [x86] Failure to use registers optimally when swapping between (identically represented) vector types gabravier at gmail dot com
2021-10-15  2:30 ` [Bug target/102758] [12 Regression] Failure to use registers optimally with return values (2 operands related) pinskia at gcc dot gnu.org
2021-10-15  2:42 ` [Bug target/102758] [12 Regression] Failure to use registers optimally with return values (2 operands related and subreg) pinskia at gcc dot gnu.org
2021-10-15  6:28 ` rguenth at gcc dot gnu.org
2021-12-03 16:37 ` rsandifo at gcc dot gnu.org [this message]
2022-05-06  8:31 ` [Bug target/102758] [12/13 " jakub at gcc dot gnu.org
2022-10-19  9:40 ` rguenth at gcc dot gnu.org
2023-05-08 12:22 ` [Bug target/102758] [12/13/14 " 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-102758-4-LbOqjZHtGq@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).