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/103660] Sub-optimal code with relational operators
Date: Tue, 20 Aug 2024 14:07:31 +0000	[thread overview]
Message-ID: <bug-103660-4-RA8Pkqtjtc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103660-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:b73373520f0ed5d131d2cd6ee9078939a98d7a0d

commit r15-3040-gb73373520f0ed5d131d2cd6ee9078939a98d7a0d
Author: Andrew Pinski <quic_apinski@quicinc.com>
Date:   Mon Aug 12 16:00:45 2024 -0700

    match: extend the `((a CMP b) ? c : 0) | ((a CMP' b) ? d : 0)` patterns to
support ^ and + [PR103660]

    r13-4620-g4d9db4bdd458 Added a few patterns and some of them can be
extended to support XOR and PLUS.
    This extends the patterns to support XOR and PLUS instead of just IOR.

    Bootstrapped and tested on x86_64-linux-gnu.

            PR tree-optimization/103660

    gcc/ChangeLog:

            * match.pd (`((a CMP b) ? c : 0) | ((a CMP' b) ? d : 0)`): Extend
to support
            XOR and PLUS.

    gcc/testsuite/ChangeLog:

            * g++.dg/tree-ssa/pr103660-2.C: New test.
            * g++.dg/tree-ssa/pr103660-3.C: New test.
            * gcc.dg/tree-ssa/pr103660-2.c: New test.
            * gcc.dg/tree-ssa/pr103660-3.c: New test.

    Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>

  parent reply	other threads:[~2024-08-20 14:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11 13:14 [Bug c/103660] New: " david at westcontrol dot com
2021-12-12 23:58 ` [Bug tree-optimization/103660] " pinskia at gcc dot gnu.org
2023-08-23  3:45 ` pinskia at gcc dot gnu.org
2023-08-23  4:45 ` pinskia at gcc dot gnu.org
2023-08-23  4:49 ` pinskia at gcc dot gnu.org
2024-08-09 18:40 ` pinskia at gcc dot gnu.org
2024-08-12 19:52 ` pinskia at gcc dot gnu.org
2024-08-12 20:17 ` pinskia at gcc dot gnu.org
2024-08-13  4:48 ` pinskia at gcc dot gnu.org
2024-08-20 14:07 ` cvs-commit at gcc dot gnu.org
2024-08-20 14:07 ` cvs-commit at gcc dot gnu.org [this message]
2024-08-20 14:07 ` cvs-commit at gcc dot gnu.org
2024-08-20 14:10 ` 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-103660-4-RA8Pkqtjtc@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).