public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105314] ifcvt regression in noce_try_store_flag_mask
Date: Wed, 20 Apr 2022 07:49:09 +0000 [thread overview]
Message-ID: <bug-105314-4-QtNfTye7J6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105314-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105314
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|tree-optimization |target
Keywords| |missed-optimization
Target| |riscv
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I observed sth similar on arm and x86_64 where the backends were adjusted to
treat two equal variants the same. The issue that is observed from the
GIMPLE level change is that the edge containing the forwarder changes and
so we get slightly different initial RTL out of it.
You have to analyze in more detail what happens.
next prev parent reply other threads:[~2022-04-20 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 20:19 [Bug tree-optimization/105314] New: " christophm30 at gmail dot com
2022-04-19 20:23 ` [Bug tree-optimization/105314] " christophm30 at gmail dot com
2022-04-20 7:10 ` marxin at gcc dot gnu.org
2022-04-20 7:10 ` marxin at gcc dot gnu.org
2022-04-20 7:49 ` rguenth at gcc dot gnu.org [this message]
2022-04-22 9:48 ` [Bug target/105314] [12 Regression] " pinskia at gcc dot gnu.org
2022-04-25 15:45 ` [Bug rtl-optimization/105314] " jakub at gcc dot gnu.org
2022-04-25 22:34 ` ptomsich at gcc dot gnu.org
2022-04-25 22:40 ` christophm30 at gmail dot com
2022-04-25 22:47 ` ptomsich at gcc dot gnu.org
2022-04-26 0:05 ` christophm30 at gmail dot com
2022-04-26 8:12 ` cvs-commit at gcc dot gnu.org
2022-04-26 8:13 ` jakub at gcc dot gnu.org
2024-01-26 21:48 ` cvs-commit 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-105314-4-QtNfTye7J6@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).