public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brycelelbach at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100986] New: internal compiler error: in finish_expr_stmt, at cp/semantics.c:681
Date: Wed, 09 Jun 2021 07:13:47 +0000 [thread overview]
Message-ID: <bug-100986-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100986
Bug ID: 100986
Summary: internal compiler error: in finish_expr_stmt, at
cp/semantics.c:681
Product: gcc
Version: 10.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: brycelelbach at gmail dot com
Target Milestone: ---
https://godbolt.org/z/7nrdxz3ax
I ran into this when doing stuff with CTAD.
It appears to be fixed in GCC 11, but since it's an ICE, I figured I'd follow a
bug report in case y'all want to bug fix it in the GCC 10.x series (or at least
make it fail more gracefully).
next reply other threads:[~2021-06-09 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 7:13 brycelelbach at gmail dot com [this message]
2021-06-09 12:15 ` [Bug c++/100986] " mpolacek 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-100986-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).