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/107270] [11/12/13/14 Regression] return for structure is not as good as before
Date: Fri, 23 Feb 2024 04:24:00 +0000 [thread overview]
Message-ID: <bug-107270-4-3FffuEnAvx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107270-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107270
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|pinskia at gcc dot gnu.org |unassigned at gcc dot gnu.org
Status|ASSIGNED |NEW
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #2)
> But this is just BFI, so it's a costing issue.
Fixing that still leaves us with:
Trying 8 -> 15:
8: zero_extract(r100:DI,0x20,0)=r107:SI#0
REG_DEAD r107:SI
15: x0:DI=r100:DI&0xffffffff|r108:SI#0<<0x20
REG_DEAD r108:SI
REG_DEAD r100:DI
Failed to match this instruction:
(set (reg/i:DI 0 x0)
(ior:DI (ashift:DI (subreg:DI (reg:SI 108) 0)
(const_int 32 [0x20]))
(zero_extend:DI (reg:SI 107))))
Which is a BFI but there is no pattern to match that.
I will submit my rtx_cost patch still but for now I am not going to add another
pattern
prev parent reply other threads:[~2024-02-23 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 1:08 [Bug rtl-optimization/107270] New: [10/11/12/13 " pinskia at gcc dot gnu.org
2022-10-15 1:08 ` [Bug rtl-optimization/107270] " pinskia at gcc dot gnu.org
2023-04-08 14:41 ` [Bug target/107270] " law at gcc dot gnu.org
2023-07-07 10:44 ` [Bug target/107270] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-02-22 15:56 ` rearnsha at gcc dot gnu.org
2024-02-23 1:21 ` pinskia at gcc dot gnu.org
2024-02-23 4:24 ` pinskia 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-107270-4-3FffuEnAvx@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).