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/100349] [11/12 Regression] ICE Segmentation fault during GIMPLE pass: evrp (under -O2 to -Os)
Date: Fri, 30 Apr 2021 14:35:38 +0000	[thread overview]
Message-ID: <bug-100349-4-yH9UXNpV1v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100349-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
evolution_part_in_loop_num() is returning NULL when evrp asks about the PHI
result here:

(gdb) p debug(stmt)
c.1_4 = PHI <c.1_1(4)>

Is this expected?

If it is, we could easily return false if step is null and everything should
just work.

  parent reply	other threads:[~2021-04-30 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30  8:26 [Bug tree-optimization/100349] New: " haoxintu at gmail dot com
2021-04-30 12:01 ` [Bug tree-optimization/100349] " rguenth at gcc dot gnu.org
2021-04-30 14:35 ` aldyh at gcc dot gnu.org [this message]
2021-05-13  0:06 ` tlwang at uwaterloo dot ca
2021-05-14 20:17 ` aldyh at gcc dot gnu.org
2021-05-17 16:19 ` cvs-commit at gcc dot gnu.org
2021-07-16 14:11 ` [Bug tree-optimization/100349] [11 " amacleod at redhat dot com

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-100349-4-yH9UXNpV1v@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).