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/97560] [11 Regression] ICE: tree check: expected tree that contains 'decl common' structure, have 'component_ref' in tree_could_trap_p, at tree-eh.c:2708 since r11-3685
Date: Sat, 24 Oct 2020 16:26:37 +0000	[thread overview]
Message-ID: <bug-97560-4-RV8cWfq9is@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97560-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
$ ./cc1plus a.c -O2 -fno-tree-forwprop -fnon-call-exc
eptions -quiet
$

Is this still an issue?  I can't reproduce on trunk, and I see the PR was
reported against a snapshot from 18-oct.  A lot has changed in trunk in a week.

  parent reply	other threads:[~2020-10-24 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-24  8:50 [Bug tree-optimization/97560] New: [11 Regression] ICE: tree check: expected tree that contains 'decl common' structure, have 'component_ref' in tree_could_trap_p, at tree-eh.c:2708 asolokha at gmx dot com
2020-10-24  8:57 ` [Bug tree-optimization/97560] " jakub at gcc dot gnu.org
2020-10-24  8:59 ` [Bug tree-optimization/97560] [11 Regression] ICE: tree check: expected tree that contains 'decl common' structure, have 'component_ref' in tree_could_trap_p, at tree-eh.c:2708 since r11-3685 jakub at gcc dot gnu.org
2020-10-24 16:26 ` aldyh at gcc dot gnu.org [this message]
2020-10-24 16:43 ` jakub at gcc dot gnu.org
2020-10-26 18:31 ` aldyh at gcc dot gnu.org
2020-10-27  6:31 ` cvs-commit at gcc dot gnu.org
2020-10-27 13:46 ` cvs-commit 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-97560-4-RV8cWfq9is@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).