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++/100632] [11/12 Regression] ICE: Segmentation fault (in write_member_name) since r11-2237 Date: Mon, 17 May 2021 08:53:14 +0000 [thread overview] Message-ID: <bug-100632-4-AYaxRGCq1G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100632-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100632 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Target Milestone|--- |11.2 Last reconfirmed| |2021-05-17 CC| |jakub at gcc dot gnu.org Summary|[11/12 Regression] ICE: |[11/12 Regression] ICE: |Segmentation fault (in |Segmentation fault (in |write_member_name) |write_member_name) since | |r11-2237 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- ICEs since r11-2237-g812798917c59e95405a71b31ab37bd78c0f43f79 Before that it has been rejected with pr100632.C:6:15: error: template-id ‘f<B{((const int*)(& nested.Nested::<anonymous>.Nested::<unnamed union>::k))}>’ for ‘void f()’ does not match any template declaration 6 | template void f<B{&nested.k}>(); | ^~~~~~~~~~~~~~~ pr100632.C:2:18: note: candidate is: ‘template<B <anonymous> > void f()’ 2 | template<B> void f(); | ^
next prev parent reply other threads:[~2021-05-17 8:53 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-17 5:54 [Bug c++/100632] New: [11/12 Regression] ICE: Segmentation fault (in write_member_name) asolokha at gmx dot com 2021-05-17 8:53 ` jakub at gcc dot gnu.org [this message] 2021-05-17 12:51 ` [Bug c++/100632] [11/12 Regression] ICE: Segmentation fault (in write_member_name) since r11-2237 rguenth at gcc dot gnu.org 2021-07-28 7:07 ` rguenth at gcc dot gnu.org 2022-04-21 7:49 ` rguenth at gcc dot gnu.org 2023-05-29 10:05 ` [Bug c++/100632] [11/12/13/14 " jakub 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-100632-4-AYaxRGCq1G@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).