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/107888] [12/13/14 Regression] Missed min/max transformation in phiopt due to VRP Date: Tue, 09 May 2023 10:19:44 +0000 [thread overview] Message-ID: <bug-107888-4-vXXNZqIYcG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107888-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107888 --- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Created attachment 55027 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55027&action=edit testcases max is optimized with this, max1 was already handled. min was already handled, min1 is optimized with this. Note at -O1, all 4 are done at phiopt1, At -O2, only max1/min are done at phiopt1 and max/min1 are handled at phiopt2 due to now having the range. Note I think having phiopt enable ranges overall might be too much overhead I so we might need to leave it this way.
next prev parent reply other threads:[~2023-05-09 10:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-27 19:28 [Bug tree-optimization/107888] New: [12/13 " pinskia at gcc dot gnu.org 2022-11-28 7:57 ` [Bug tree-optimization/107888] " rguenth at gcc dot gnu.org 2022-11-28 17:26 ` pinskia at gcc dot gnu.org 2022-12-21 13:35 ` rguenth at gcc dot gnu.org 2023-05-06 0:38 ` [Bug tree-optimization/107888] [12/13/14 " pinskia at gcc dot gnu.org 2023-05-08 5:35 ` pinskia at gcc dot gnu.org 2023-05-08 12:26 ` rguenth at gcc dot gnu.org 2023-05-09 10:14 ` pinskia at gcc dot gnu.org 2023-05-09 10:19 ` pinskia at gcc dot gnu.org [this message] 2023-05-10 18:11 ` pinskia at gcc dot gnu.org 2023-05-10 19:10 ` pinskia at gcc dot gnu.org 2023-05-16 3:50 ` 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-107888-4-vXXNZqIYcG@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).