public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106862] New: ice in compute_control_dep_chain, at gimple-predicate-analysis.cc:1105
Date: Tue, 06 Sep 2022 17:35:08 +0000	[thread overview]
Message-ID: <bug-106862-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106862
           Summary: ice in compute_control_dep_chain, at
                    gimple-predicate-analysis.cc:1105
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

Created attachment 53545
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53545&action=edit
gzipped C++ source code

For the attached C++ code, recent g++ does this:

$ /home/dcb/gcc/results/bin/g++ -c -g -O1 -Wall -fpermissive bug842.cc
during GIMPLE pass: uninit
In file included from VSLRead.C:113:
y.tab.c: In function ‘int VSLLib_parse()’:
y.tab.c:1497:1: internal compiler error: in compute_control_dep_chain, at
gimple-predicate-analysis.cc:1105
0x1df8e69 compute_control_dep_chain(basic_block_def*, basic_block_def const*,
vec<edge_def*, va_heap, vl_ptr>*, uns
igned int*, vec<edge_def*, va_heap, vl_ptr>&, unsigned int*, unsigned int,
unsigned int)
        ../../trunk.git/gcc/gimple-predicate-analysis.cc:1105
0x1df8ae7 compute_control_dep_chain(basic_block_def*, basic_block_def const*,
vec<edge_def*, va_heap, vl_ptr>*, uns
igned int*, vec<edge_def*, va_heap, vl_ptr>&, unsigned int*, unsigned int,
unsigned int)
        ../../trunk.git/gcc/gimple-predicate-analysis.cc:1086
0x1df8ae7 compute_control_dep_chain(basic_block_def*, basic_block_def const*,
vec<edge_def*, va_heap, vl_ptr>*, uns
igned int*, vec<edge_def*, va_heap, vl_ptr>&, unsigned int*, unsigned int,
unsigned int)
        ../../trunk.git/gcc/gimple-predicate-analysis.cc:1086
0x1df7895 compute_control_dep_chain(basic_block_def*, basic_block_def const*,
vec<edge_def*, va_heap, vl_ptr>*, uns
igned int*, unsigned int)
        ../../trunk.git/gcc/gimple-predicate-analysis.cc:1120

The bug first seems to occur sometime between git hash 5e070cf4bd085e10,
from yesterday, and d6582c662ca0da05, from today.

             reply	other threads:[~2022-09-06 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 17:35 dcb314 at hotmail dot com [this message]
2022-09-06 17:55 ` [Bug tree-optimization/106862] " dcb314 at hotmail dot com
2022-09-06 21:39 ` dcb314 at hotmail dot com
2022-09-07  8:28 ` dcb314 at hotmail dot com
2022-09-07  8:55 ` 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-106862-4@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).