public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/100505] ICE: in record_in_finally_tree, at tree-eh.c:213
Date: Mon, 10 May 2021 14:20:23 +0000	[thread overview]
Message-ID: <bug-100505-4-MFtpiVTscS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100505-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
__GIMPLE and __RTL expects correct input and handles just limited diagnostics.
I think especially error-recovery for these are WONTFIX.

  reply	other threads:[~2021-05-10 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 14:13 [Bug c/100505] New: " cnsun at uwaterloo dot ca
2021-05-10 14:20 ` jakub at gcc dot gnu.org [this message]
2021-05-10 14:24 ` [Bug c/100505] " cnsun at uwaterloo dot ca
2021-05-12 10:30 ` rguenth at gcc dot gnu.org
2022-01-04  2:34 ` pinskia 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-100505-4-MFtpiVTscS@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).