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/94920] Failure to optimize abs pattern from arithmetic with selected operands based on comparisons with 0 Date: Sat, 14 Aug 2021 23:58:42 +0000 [thread overview] Message-ID: <bug-94920-4-3Pji7WZCt8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94920-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94920 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2020-05-04 00:00:00 |2021-8-14 Severity|normal |enhancement --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- if (x_4(D) <= 0) goto <bb 3>; [INV] else goto <bb 4>; [INV] <bb 3> : iftmp.0_6 = -x_4(D); <bb 4> : # iftmp.0_3 = PHI <iftmp.0_6(3), 0(2)> x <= 0 ? -x : 0 isn't this MAX<-x, 0>? So there are two issues here, first is the above one, the second one is MAX<a, 0> + MAX<-a,0> is not optimized to just MAX<-a,a> or just ABS<a>. E.g.: unsigned f1(int x) { int t = (x >= 0 ? x : 0) ; int tt = -x; int t1 = (tt >= 0 ? tt : 0) ; return t + t1; }
next prev parent reply other threads:[~2021-08-14 23:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-02 10:53 [Bug tree-optimization/94920] New: " gabravier at gmail dot com 2020-05-04 6:37 ` [Bug tree-optimization/94920] " rguenth at gcc dot gnu.org 2021-08-14 23:58 ` pinskia at gcc dot gnu.org [this message] 2022-07-21 21:27 ` cvs-commit at gcc dot gnu.org 2022-07-27 10:04 ` cvs-commit at gcc dot gnu.org 2022-07-27 10:27 ` gabravier at gmail dot com 2022-08-06 8:14 ` paul.hua.gm at gmail dot com 2022-08-25 22:20 ` pinskia at gcc dot gnu.org 2022-08-25 22:23 ` pinskia at gcc dot gnu.org 2022-10-14 17:56 ` danglin at gcc dot gnu.org 2023-03-04 22:35 ` sandra at gcc dot gnu.org 2023-09-17 16:44 ` 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-94920-4-3Pji7WZCt8@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).