public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95649] [11 Regression] ICE during GIMPLE pass: cunroll since r11-1146-g1396fa5b91cfa0b3
Date: Tue, 16 Jun 2020 18:59:38 +0000	[thread overview]
Message-ID: <bug-95649-4-y6McUu1FA2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95649-4@http.gcc.gnu.org/bugzilla/>

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

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #10 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #8)
> I still don't understand why propagating one SSA_NAME for another is causing
> headaches later though. 

TBH, I don't either.

When I compile the .c test in this PR with the following options:

-O2 -fno-tree-scev-cprop -fdisable-tree-ccp1  -fdisable-tree-ccp2
-fdisable-tree-copyprop1 -fdisable-tree-evrp -fdisable-tree-vrp1
-fdisable-tree-ccp1 -fdisable-tree-ccp2 -fdisable-tree-ccp3

...I still get an ICE, but there is no change in the IL between trunk without
the offending patch, and with the patch that broke the test.  This would
indicate that there is some on-the-side structure that is being altered by the
phi argument propagation.

I did notice that the IL *does* change in the middle of one of the copyprop (or
ccp?) passes, but it gets cleaned up to whatever was there before.

Later in SCEV, we ICE while trying to look at the SSA_NAME_DEF_STMT of an SSA
which no longer exists in the IL.  This happens in
chrec_contains_symbols_defined_in_loop().  A wild guess is that the loop info
is getting mucked up somehow.

I can investigate more deeply if desired, but since this was a silly typo, I'm
gonna leave it alone for now.

Closing as fixed in mainline.

      parent reply	other threads:[~2020-06-16 18:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12  5:45 [Bug tree-optimization/95649] New: ICE during GIMPLE pass: cunroll vsevolod.livinskij at frtk dot ru
2020-06-12  7:28 ` [Bug tree-optimization/95649] [11 Regression] ICE during GIMPLE pass: cunroll since r11-1146-g1396fa5b91cfa0b3 marxin at gcc dot gnu.org
2020-06-12  8:03 ` rguenth at gcc dot gnu.org
2020-06-14 14:05 ` seurer at linux dot vnet.ibm.com
2020-06-15 17:20 ` aldyh at gcc dot gnu.org
2020-06-15 17:21 ` aldyh at gcc dot gnu.org
2020-06-15 17:21 ` aldyh at gcc dot gnu.org
2020-06-15 18:12 ` aldyh at gcc dot gnu.org
2020-06-15 19:11 ` law at redhat dot com
2020-06-16 11:56 ` aldyh at gcc dot gnu.org
2020-06-16 14:23 ` law at redhat dot com
2020-06-16 18:51 ` cvs-commit at gcc dot gnu.org
2020-06-16 18:59 ` aldyh at gcc dot gnu.org [this message]

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-95649-4-y6McUu1FA2@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).