public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/94589] Optimize (i<=>0)>0 to i>0 Date: Fri, 30 Apr 2021 17:23:10 +0000 [thread overview] Message-ID: <bug-94589-4-iTMCdq0yLl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94589-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94589 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #50710|0 |1 is obsolete| | --- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 50719 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50719&action=edit gcc12-pr94589-wip.patch Updated patch. This already does the optimizations, though needs testcase coverage and perhaps something better for debug uses of the PHI_RESULT besides the single non-debug use. And, it won't work together with the above mentioned forwprop patch, I'm afraid it would need to virtually undo that change but it would be hard.
next prev parent reply other threads:[~2021-04-30 17:23 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-14 6:57 [Bug tree-optimization/94589] New: " glisse at gcc dot gnu.org 2020-04-14 10:43 ` [Bug tree-optimization/94589] " rguenth at gcc dot gnu.org 2020-06-05 15:31 ` khim at google dot com 2021-04-29 8:55 ` redi at gcc dot gnu.org 2021-04-29 8:57 ` redi at gcc dot gnu.org 2021-04-29 9:21 ` redi at gcc dot gnu.org 2021-04-29 10:07 ` rguenth at gcc dot gnu.org 2021-04-29 10:25 ` glisse at gcc dot gnu.org 2021-04-29 10:28 ` glisse at gcc dot gnu.org 2021-04-29 10:33 ` redi at gcc dot gnu.org 2021-04-29 10:33 ` redi at gcc dot gnu.org 2021-04-29 10:39 ` rguenther at suse dot de 2021-04-29 11:06 ` glisse at gcc dot gnu.org 2021-04-29 11:49 ` rguenth at gcc dot gnu.org 2021-04-29 12:55 ` rguenth at gcc dot gnu.org 2021-04-29 13:29 ` jakub at gcc dot gnu.org 2021-04-29 15:48 ` jakub at gcc dot gnu.org 2021-04-29 17:41 ` jakub at gcc dot gnu.org 2021-04-30 17:23 ` jakub at gcc dot gnu.org [this message] 2021-05-03 17:09 ` jakub at gcc dot gnu.org 2021-05-06 8:18 ` cvs-commit at gcc dot gnu.org 2021-05-12 7:48 ` cvs-commit at gcc dot gnu.org 2021-05-18 8:09 ` cvs-commit at gcc dot gnu.org 2021-05-18 8:11 ` jakub at gcc dot gnu.org 2021-05-20 7:11 ` cvs-commit at gcc dot gnu.org 2021-05-21 8:40 ` cvs-commit at gcc dot gnu.org 2021-08-27 6:15 ` pinskia at gcc dot gnu.org 2023-09-13 18:09 ` pinskia 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-94589-4-iTMCdq0yLl@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).