public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97995] [8/9/10/11 Regression] ICE tree check: expected tree that contains 'typed' structure, have 'deferred_noexcept' in unify, at cp/pt.c:23473 since r7-4383-g51dc660315ef83dc Date: Mon, 30 Nov 2020 17:17:12 +0000 [thread overview] Message-ID: <bug-97995-4-RDtyteEcNF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97995-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97995 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> --- This also ICEs, but in a different spot: struct S; template <class T> void foo () noexcept (T::v); template <class ...A, int b> void bar (void (A...) noexcept (1)); static_assert (bar (foo<S>));
next prev parent reply other threads:[~2020-11-30 17:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-25 17:11 [Bug c++/97995] New: [11 Regression] ICE tree check: expected tree that contains 'typed' structure, have 'deferred_noexcept' in unify, at cp/pt.c:23473 gscfq@t-online.de 2020-11-26 10:13 ` [Bug c++/97995] [8/9/10/11 Regression] ICE tree check: expected tree that contains 'typed' structure, have 'deferred_noexcept' in unify, at cp/pt.c:23473 since r7-4383-g51dc660315ef83dc marxin at gcc dot gnu.org 2020-11-26 10:13 ` rguenth at gcc dot gnu.org 2020-11-26 10:13 ` rguenth at gcc dot gnu.org 2020-11-30 17:17 ` mpolacek at gcc dot gnu.org [this message] 2021-01-14 9:47 ` rguenth at gcc dot gnu.org 2021-04-09 15:21 ` ppalka at gcc dot gnu.org 2021-04-09 15:25 ` 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-97995-4-RDtyteEcNF@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).