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/106630] [13 Regression] ICE: Segmentation fault signal terminated program cc1plus with -O2 since r13-1268-g8c99e307b20c50
Date: Mon, 15 Aug 2022 22:09:05 +0000	[thread overview]
Message-ID: <bug-106630-4-c57gg6bSNU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106630-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> > It looks like DOM2, as a side-effect of using the ranger to do cprop, is
> > exporting a global range for a_9 
> > Where a_9 has a global range of [0,0].
> 
> Why didn't DOM do a constant prop here since the only value for a_9 is 0 ...

The only uses of a_9 are in PHIs:

  <bb 5> [local count: 4724464]:
  # a_9 = PHI <a_13(4), 0(3)>
  goto <bb 8>; [100.00%]
...
...
  <bb 8> [local count: 42949672]:
  # a_23 = PHI <a_14(7), a_9(5)>
  goto <bb 6>; [100.00%]

Perhaps DOM doesn't cprop into PHIs?

....actually:

static void
cprop_into_successor_phis (basic_block bb,
                           class const_and_copies *const_and_copies)

But that only works with DOM's internal const_and_copies tables, not with
ranger (or originally with the evrp engine).

  parent reply	other threads:[~2022-08-15 22:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 17:28 [Bug tree-optimization/106630] New: [13 Regression] ICE: Segmentation fault signal terminated program cc1plus with -O2 vsevolod.livinskiy at gmail dot com
2022-08-15 17:33 ` [Bug tree-optimization/106630] " pinskia at gcc dot gnu.org
2022-08-15 17:45 ` mpolacek at gcc dot gnu.org
2022-08-15 19:27 ` [Bug tree-optimization/106630] [13 Regression] ICE: Segmentation fault signal terminated program cc1plus with -O2 since r13-1268-g8c99e307b20c50 aldyh at gcc dot gnu.org
2022-08-15 21:34 ` aldyh at gcc dot gnu.org
2022-08-15 21:39 ` pinskia at gcc dot gnu.org
2022-08-15 22:09 ` aldyh at gcc dot gnu.org [this message]
2022-08-16  7:41 ` rguenth at gcc dot gnu.org
2022-08-16  7:47 ` aldyh at gcc dot gnu.org
2022-08-16  7:54 ` rguenther at suse dot de
2022-08-16  9:20 ` cvs-commit at gcc dot gnu.org
2022-08-16  9:21 ` rguenth 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-106630-4-c57gg6bSNU@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).