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/103228] [9/10/11/12 Regression] missed optimization with |^ at the gimple level
Date: Wed, 17 Nov 2021 23:40:14 +0000	[thread overview]
Message-ID: <bug-103228-4-1xuf00mszP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103228-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 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:32221357007666124409ec3ee0d3a1cf263ebc9e

commit r12-5358-g32221357007666124409ec3ee0d3a1cf263ebc9e
Author: Andrew Pinski <apinski@marvell.com>
Date:   Mon Nov 15 09:31:20 2021 +0000

    Fix PR tree-optimization/103228 and 103228: folding of (type) X op CST
where type is a nop convert

    Currently we fold (type) X op CST into (type) (X op ((type-x) CST)) when
the conversion widens
    but not when the conversion is a nop. For the same reason why we move the
widening conversion
    (the possibility of removing an extra conversion), we should do the same if
the conversion is a
    nop.

    Committed as approved with the comment change.

            PR tree-optimization/103228
            PR tree-optimization/55177

    gcc/ChangeLog:

            * match.pd ((type) X bitop CST): Also do this
            transformation for nop conversions.

    gcc/testsuite/ChangeLog:

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

  parent reply	other threads:[~2021-11-17 23:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14  6:30 [Bug tree-optimization/103228] New: " pinskia at gcc dot gnu.org
2021-11-14  6:30 ` [Bug tree-optimization/103228] " pinskia at gcc dot gnu.org
2021-11-15  8:34 ` pinskia at gcc dot gnu.org
2021-11-15  8:37 ` pinskia at gcc dot gnu.org
2021-11-15  9:06 ` rguenth at gcc dot gnu.org
2021-11-15  9:07 ` rguenth at gcc dot gnu.org
2021-11-15  9:14 ` pinskia at gcc dot gnu.org
2021-11-16  3:32 ` cvs-commit at gcc dot gnu.org
2021-11-16  3:33 ` pinskia at gcc dot gnu.org
2021-11-16  3:36 ` pinskia at gcc dot gnu.org
2021-11-17 23:40 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-17 23:40 ` 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-103228-4-1xuf00mszP@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).