public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99806] New: ICE in tsubst_copy of gcc-trunk and tree_code_size of gcc-10 Date: Mon, 29 Mar 2021 04:53:55 +0000 [thread overview] Message-ID: <bug-99806-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99806 Bug ID: 99806 Summary: ICE in tsubst_copy of gcc-trunk and tree_code_size of gcc-10 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: hewillk at gmail dot com Target Milestone: --- https://godbolt.org/z/s687ePeGG template <class T> concept C = requires (T a) { a.f(0); }; struct S { void f(auto) noexcept(); }; static_assert(C<S>); gcc-trunk: <source>:2:17: internal compiler error: in tsubst_copy, at cp/pt.c:17247 2 | struct S { void f(auto) noexcept(); }; | ^ gcc-10: <source>:2:17: internal compiler error: in tree_code_size, at tree.c:910 2 | struct S { void f(auto) noexcept(); }; |
next reply other threads:[~2021-03-29 4:53 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-29 4:53 hewillk at gmail dot com [this message] 2021-03-29 17:40 ` [Bug c++/99806] [10/11 Regression] ICE: in tsubst_copy, at cp/pt.c:17247 mpolacek at gcc dot gnu.org 2021-03-29 17:40 ` mpolacek at gcc dot gnu.org 2021-04-07 21:20 ` mpolacek at gcc dot gnu.org 2021-04-08 1:13 ` mpolacek at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-08 17:44 ` mpolacek at gcc dot gnu.org 2021-04-08 19:14 ` mpolacek at gcc dot gnu.org 2021-04-09 14:29 ` cvs-commit at gcc dot gnu.org 2021-04-09 14:32 ` [Bug c++/99806] [10 " mpolacek at gcc dot gnu.org 2021-04-09 14:51 ` ppalka at gcc dot gnu.org 2021-04-09 22:47 ` cvs-commit at gcc dot gnu.org 2021-04-09 22:48 ` 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-99806-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: linkBe 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).