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 tree-optimization/67962] Optimization opportunity with conditional swap to two MIN/MAX in phiopt Date: Wed, 14 Oct 2015 11:44:00 -0000 [thread overview] Message-ID: <bug-67962-4-kSnFamsJKq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67962-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67962 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Status|UNCONFIRMED |NEW Last reconfirmed| |2015-10-14 Component|c++ |tree-optimization Summary|Optimization opportunity |Optimization opportunity |with conditional swap |with conditional swap to | |two MIN/MAX in phiopt Ever confirmed|0 |1 Severity|minor |enhancement --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- We miss the opportunity to turn <bb 2>: if (y_5(D) < x_6(D)) goto <bb 4>; else goto <bb 3>; <bb 3>: <bb 4>: # y_4 = PHI <y_5(D)(3), x_6(D)(2)> # x_2 = PHI <x_6(D)(3), y_5(D)(2)> into y_4 = MAX (x_6, y_5); x_2 = MIN (x_6, y_5); and further optimize MINMAX (ISTR that was suggested elsewhere). phiopt only considers a single min/max operation. Now the question is whether the transform would be profitable in isolation.
next prev parent reply other threads:[~2015-10-14 11:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-14 11:06 [Bug c++/67962] New: Optimization opportunity with conditional swap morwenn29 at hotmail dot fr 2015-10-14 11:44 ` rguenth at gcc dot gnu.org [this message] 2021-08-30 5:45 ` [Bug tree-optimization/67962] Optimization opportunity with conditional swap to two MIN/MAX in phiopt pinskia at gcc dot gnu.org 2023-07-21 8:26 ` rguenth 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-67962-4-kSnFamsJKq@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).