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/88575] gcc got confused by different comparison operators Date: Fri, 09 Jun 2023 22:24:48 +0000 [thread overview] Message-ID: <bug-88575-4-oU1boy0Qnq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88575-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88575 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2019-01-02 00:00:00 |2023-6-9 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So VRP handles floating point now but it still does not optimize it: Folding statement: if (a_2(D) <= b_3(D)) Registering value_relation (a_2(D) <= b_3(D)) on (2->3) Visiting conditional with predicate: if (a_2(D) <= b_3(D)) With known ranges a_2(D): [frange] double VARYING b_3(D): [frange] double VARYING Predicate evaluates to: DON'T KNOW Not folded Folding statement: _4 = MIN_EXPR <a_2(D), b_3(D)>; Not folded While the int does this: Folding statement: _4 = MIN_EXPR <a_2(D), b_3(D)>; folding with relation a_2(D) <= b_3(D) Global Exported: _4 = [irange] int [-INF, 2147483646] Not folded Which is a regression from GCC 12 ....
next prev parent reply other threads:[~2023-06-09 22:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88575-4@http.gcc.gnu.org/bugzilla/> 2021-07-24 10:18 ` pinskia at gcc dot gnu.org 2023-06-09 22:24 ` pinskia at gcc dot gnu.org [this message] 2023-06-09 22:28 ` 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-88575-4-oU1boy0Qnq@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).