public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95820] [10 Regression] ICE in splice_late_return_type, at cp/pt.c:29034 Date: Sun, 26 Jul 2020 18:43:49 +0000 [thread overview] Message-ID: <bug-95820-4-dRu73EATnt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95820-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95820 Sergei Trofimovich <slyfox at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |slyfox at gcc dot gnu.org --- Comment #8 from Sergei Trofimovich <slyfox at gcc dot gnu.org> --- In https://bugs.gentoo.org/730406 we see it on gcc-10.2.0 as well. Minimal example: $ cat a.cc template <long()()->decltype(0) $ LANG=C gcc-10.2.0 a.cc a.cc:1:21: internal compiler error: in splice_late_return_type, at cp/pt.c:29152 Should it be backported to gcc-10?
next prev parent reply other threads:[~2020-07-26 18:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-22 15:01 [Bug c++/95820] New: " haoxintu at gmail dot com 2020-06-22 15:07 ` [Bug c++/95820] " haoxintu at gmail dot com 2020-06-22 15:21 ` mpolacek at gcc dot gnu.org 2020-06-24 17:05 ` mpolacek at gcc dot gnu.org 2020-06-24 18:50 ` [Bug c++/95820] [10/11 Regression] " mpolacek at gcc dot gnu.org 2020-06-24 19:47 ` mpolacek at gcc dot gnu.org 2020-06-27 14:51 ` mpolacek at gcc dot gnu.org 2020-07-14 13:42 ` cvs-commit at gcc dot gnu.org 2020-07-14 13:44 ` [Bug c++/95820] [10 " mpolacek at gcc dot gnu.org 2020-07-26 18:43 ` slyfox at gcc dot gnu.org [this message] 2020-07-27 1:06 ` mpolacek at gcc dot gnu.org 2020-07-27 7:08 ` slyfox 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-95820-4-dRu73EATnt@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).