public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96681] Failure to optimize xor of comparisons with specific constants to comparison of xor-ed of compared variables
Date: Fri, 15 Jan 2021 20:11:25 +0000	[thread overview]
Message-ID: <bug-96681-4-MheDqM3PoE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96681-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96681

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:5c046034e3ea61dd68965154a398f8f813daf8f2

commit r11-6738-g5c046034e3ea61dd68965154a398f8f813daf8f2
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Jan 15 21:10:44 2021 +0100

    match.pd: Optimize (x < 0) ^ (y < 0) to (x ^ y) < 0 etc. [PR96681]

    This patch simplifies comparisons that test the sign bit xored together.
    If the comparisons are both < 0 or both >= 0, then we should xor the
operands
    together and compare the result to < 0, if the comparisons are different,
    we should compare to >= 0.

    2021-01-15  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/96681
            * match.pd ((x < 0) ^ (y < 0) to (x ^ y) < 0): New simplification.
            ((x >= 0) ^ (y >= 0) to (x ^ y) < 0): Likewise.
            ((x < 0) ^ (y >= 0) to (x ^ y) >= 0): Likewise.
            ((x >= 0) ^ (y < 0) to (x ^ y) >= 0): Likewise.

            * gcc.dg/tree-ssa/pr96681.c: New test.

  parent reply	other threads:[~2021-01-15 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 16:36 [Bug tree-optimization/96681] New: " gabravier at gmail dot com
2020-08-25 10:47 ` [Bug tree-optimization/96681] " rguenth at gcc dot gnu.org
2021-01-15 13:22 ` jakub at gcc dot gnu.org
2021-01-15 20:11 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-15 20:14 ` jakub at gcc dot gnu.org
2022-11-28 22:42 ` 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-96681-4-MheDqM3PoE@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: link
Be 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).