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/94786] New: Missed min/max pattern using xor+and+less Date: Mon, 27 Apr 2020 08:11:06 +0000 [thread overview] Message-ID: <bug-94786-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94786 Bug ID: 94786 Summary: Missed min/max pattern using xor+and+less Product: gcc Version: 10.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 r1(int x, int y) { return y ^ ((x ^ y) & -(x < y)); } int r2(int x, int y) { return x ^ ((x ^ y) & -(x < y)); } `r1` can be optimized to `min` and `r2` to `max`. This transformation is done by LLVM, but not by GCC. Comparison here: https://godbolt.org/z/hNhkqM
next reply other threads:[~2020-04-27 8:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-27 8:11 gabravier at gmail dot com [this message] 2020-04-27 10:29 ` [Bug tree-optimization/94786] " rguenth at gcc dot gnu.org 2020-05-07 16:31 ` jakub at gcc dot gnu.org 2020-05-07 16:44 ` jakub at gcc dot gnu.org 2020-05-08 8:55 ` cvs-commit at gcc dot gnu.org 2020-05-08 8:56 ` jakub 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-94786-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).