public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105546] [11/12/13 Regression] ifconversion introduces many compares with loads
Date: Fri, 13 Jan 2023 21:30:28 +0000 [thread overview]
Message-ID: <bug-105546-4-8tddwviTmK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105546-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105546
Roger Sayle <roger at nextmovesoftware dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |roger at nextmovesoftware dot com
--- Comment #6 from Roger Sayle <roger at nextmovesoftware dot com> ---
The duplication of comparisons during if-conversion was tackled by this patch:
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609296.html
but unfortunately logic errors with that patch caused PR target/108292.
next prev parent reply other threads:[~2023-01-13 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 11:34 [Bug rtl-optimization/105546] New: load introduction when copying a struct absoler at smail dot nju.edu.cn
2022-05-10 11:44 ` [Bug rtl-optimization/105546] load introduction when initializing " absoler at smail dot nju.edu.cn
2022-05-10 21:02 ` [Bug target/105546] [11/12/13 Regression] ifconversion introduces many compares with loads pinskia at gcc dot gnu.org
2022-05-11 7:20 ` rguenth at gcc dot gnu.org
2022-10-19 10:06 ` rguenth at gcc dot gnu.org
2022-10-19 10:07 ` rguenth at gcc dot gnu.org
2023-01-13 21:30 ` roger at nextmovesoftware dot com [this message]
2023-05-29 10:07 ` [Bug target/105546] [11/12/13/14 " jakub 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-105546-4-8tddwviTmK@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).