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 tree-optimization/101541] Missing ABSU detection at gimple Date: Sun, 15 Oct 2023 19:24:10 +0000 [thread overview] Message-ID: <bug-101541-4-CtPhhiGH8E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101541-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101541 --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Created attachment 56118 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56118&action=edit Patch which I am testing which allows for more (independent of the other) This patch improves the case where we have a conversion at the end (after the negate expression). And with both of these patches together we are able to catch almost all. There is one more phi-opt patch needed to catch the case where the conversion before the negate expression is conditional but that is for another day.
next prev parent reply other threads:[~2023-10-15 19:24 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-20 22:58 [Bug tree-optimization/101541] New: " pinskia at gcc dot gnu.org 2021-07-21 7:01 ` [Bug tree-optimization/101541] " rguenth at gcc dot gnu.org 2021-11-20 10:58 ` pinskia at gcc dot gnu.org 2021-11-20 22:03 ` pinskia at gcc dot gnu.org 2023-05-04 0:01 ` pinskia at gcc dot gnu.org 2023-10-15 16:59 ` pinskia at gcc dot gnu.org 2023-10-15 17:42 ` pinskia at gcc dot gnu.org 2023-10-15 19:24 ` pinskia at gcc dot gnu.org [this message] 2023-10-15 22:00 ` pinskia at gcc dot gnu.org 2023-10-16 17:11 ` cvs-commit at gcc dot gnu.org 2023-10-16 17:15 ` pinskia at gcc dot gnu.org 2023-10-24 11:17 ` 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-101541-4-CtPhhiGH8E@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: linkBe 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).