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/109722] ABSU<a> == 0 is not optimized to just a == 0
Date: Fri, 05 May 2023 05:23:20 +0000	[thread overview]
Message-ID: <bug-109722-4-maGCH3zEUz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109722-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS 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:6fe385eac6ff8ecddb6cbdff2c706b27b5137006

commit r14-488-g6fe385eac6ff8ecddb6cbdff2c706b27b5137006
Author: Andrew Pinski <apinski@marvell.com>
Date:   Thu May 4 23:37:51 2023 +0000

    MATCH: Add ABSU<a> == 0 to a == 0 simplification

    There is already an `ABS<a> == 0` to `a == 0` pattern,
    this just extends that to ABSU too.

    OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions.

            PR tree-optimization/109722

    gcc/ChangeLog:

            * match.pd: Extend the `ABS<a> == 0` pattern
            to cover `ABSU<a> == 0` too.

    gcc/testsuite/ChangeLog:

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

  parent reply	other threads:[~2023-05-05  5:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  0:40 [Bug tree-optimization/109722] New: " pinskia at gcc dot gnu.org
2023-05-04  0:41 ` [Bug tree-optimization/109722] " pinskia at gcc dot gnu.org
2023-05-04  0:42 ` pinskia at gcc dot gnu.org
2023-05-04  3:35 ` pinskia at gcc dot gnu.org
2023-05-04 23:41 ` pinskia at gcc dot gnu.org
2023-05-05  5:23 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-05  5:24 ` 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-109722-4-maGCH3zEUz@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).