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/103288] [12 Regression] ice during GIMPLE pass: phiopt
Date: Wed, 17 Nov 2021 08:05:38 +0000	[thread overview]
Message-ID: <bug-103288-4-klwrwQS9wW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103288-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 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:1a15a91a0015208eafb797e4de1348c9877fd6d0

commit r12-5333-g1a15a91a0015208eafb797e4de1348c9877fd6d0
Author: Andrew Pinski <apinski@marvell.com>
Date:   Tue Nov 16 23:37:08 2021 +0000

    Fix PR 103288, ICE after PHI-OPT, move an assigment when still in use for
another bb

    The problem is r12-5300-gf98f373dd822b35c allows phiopt to recognize more
basic blocks
    but missed one location where phiopt could move an assignment from the
middle block
    to the non-middle one.  This patch fixes that.

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

            PR tree-optimization/103288

    gcc/ChangeLog:

            * tree-ssa-phiopt.c (value_replacement): Return early if middle
            block has more than one pred.

    gcc/testsuite/ChangeLog:

            * gcc.c-torture/compile/pr103288-1.c: New test.

  parent reply	other threads:[~2021-11-17  8:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 21:38 [Bug c/103288] New: " dcb314 at hotmail dot com
2021-11-16 21:43 ` [Bug tree-optimization/103288] [12 Regression] " pinskia at gcc dot gnu.org
2021-11-16 21:44 ` dcb314 at hotmail dot com
2021-11-16 21:52 ` dcb314 at hotmail dot com
2021-11-16 22:18 ` pinskia at gcc dot gnu.org
2021-11-16 22:47 ` pinskia at gcc dot gnu.org
2021-11-16 22:50 ` pinskia at gcc dot gnu.org
2021-11-16 23:12 ` pinskia at gcc dot gnu.org
2021-11-16 23:31 ` pinskia at gcc dot gnu.org
2021-11-16 23:34 ` pinskia at gcc dot gnu.org
2021-11-17  0:13 ` pinskia at gcc dot gnu.org
2021-11-17  7:47 ` pinskia at gcc dot gnu.org
2021-11-17  8:05 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-17  8:06 ` 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-103288-4-klwrwQS9wW@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).