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++/95870] ICE(segmentation fault) in most_general_template(), in gcc/cp/pt.c Date: Wed, 24 Jun 2020 17:23:29 +0000 [thread overview] Message-ID: <bug-95870-4-cEyupApvuu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95870-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95870 --- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Reduced, but invalid: template <typename> class a { public: a(); int b = [] { enum E {}; }; }; class c : a<int> { c(); }; template <typename d> a<d>::a() = default; c::c() {}
next prev parent reply other threads:[~2020-06-24 17:23 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-24 15:30 [Bug c++/95870] New: " viktor.rosendahl at bmw dot de 2020-06-24 16:46 ` [Bug c++/95870] " mpolacek at gcc dot gnu.org 2020-06-24 16:46 ` mpolacek at gcc dot gnu.org 2020-06-24 17:22 ` mpolacek at gcc dot gnu.org 2020-06-24 17:23 ` mpolacek at gcc dot gnu.org [this message] 2020-06-24 18:05 ` [Bug c++/95870] [8/9/10/11 Regression] ICE (segmentation " mpolacek at gcc dot gnu.org 2020-10-12 12:52 ` rguenth at gcc dot gnu.org 2021-03-12 0:37 ` mpolacek at gcc dot gnu.org 2021-03-12 0:37 ` mpolacek at gcc dot gnu.org 2021-04-05 13:53 ` jason at gcc dot gnu.org 2021-04-05 13:53 ` viktor.rosendahl at bmw dot de 2021-04-05 19:39 ` cvs-commit at gcc dot gnu.org 2021-04-05 21:30 ` [Bug c++/95870] [8/9/10 " jason at gcc dot gnu.org 2021-05-14 9:53 ` [Bug c++/95870] [9/10 " jakub at gcc dot gnu.org 2021-05-14 16:11 ` cvs-commit at gcc dot gnu.org 2021-05-20 21:35 ` cvs-commit at gcc dot gnu.org 2021-06-01 8:17 ` rguenth at gcc dot gnu.org 2022-05-13 17:41 ` [Bug c++/95870] [9 " cvs-commit at gcc dot gnu.org 2022-05-13 17:46 ` jason 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-95870-4-cEyupApvuu@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).