public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gabravier at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95185] New: Failure to optimize specific kind of sign comparison check Date: Mon, 18 May 2020 12:05:22 +0000 [thread overview] Message-ID: <bug-95185-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95185 Bug ID: 95185 Summary: Failure to optimize specific kind of sign comparison check Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: gabravier at gmail dot com Target Milestone: --- int f(int x, int y) { return (x >= 0) == (y <= 0); } https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94718 was resolved and most of the patterns are now optimized, but this specific one isn't. It's equivalent to `(x < 0) ^ (y <= 0)`, which can be done with a single compare instead of two. That transformation is made by LLVM, but not by GCC.
next reply other threads:[~2020-05-18 12:05 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-18 12:05 gabravier at gmail dot com [this message] 2020-05-18 13:15 ` [Bug tree-optimization/95185] " rguenth at gcc dot gnu.org 2020-05-18 13:16 ` rguenth at gcc dot gnu.org 2021-10-04 23:02 ` arjun.is at lostca dot se 2021-10-04 23:12 ` pinskia at gcc dot gnu.org 2023-06-18 19:24 ` pinskia at gcc dot gnu.org 2023-08-28 20:36 ` pinskia at gcc dot gnu.org 2023-08-28 21:08 ` pinskia at gcc dot gnu.org 2023-08-29 4:04 ` pinskia at gcc dot gnu.org 2023-09-11 22:14 ` [Bug tree-optimization/95185] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2024-03-22 14:09 ` law 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-95185-4@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).