public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "public at enkore dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97372] Segmentation fault using Tracy 0.7.3 in template class Date: Sun, 11 Oct 2020 20:25:14 +0000 [thread overview] Message-ID: <bug-97372-4-i0SBkTsNsg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97372-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97372 --- Comment #3 from marian <public at enkore dot de> --- Created attachment 49344 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49344&action=edit CVise differently reduced reproducer (possibly a different bug as well) Attached automatically reduced reproducer does retain more of the structure of the original test case, but also strikes me as suspiciously invalid C++, so probably is another bug still. $ g++ testcase_proper.ii testcase_proper.ii: In instantiation of ‘a< <template-parameter-1-1> >::a() [with <template-parameter-1-1> = int]’: testcase_proper.ii:6:19: required from here testcase_proper.ii:2:25: internal compiler error: Segmentation fault 2 | int b{[] { static int c; }}; | ^ $ cat testcase_proper.ii template <typename> class a { int b{[] { static int c; }}; public: a() {} }; void d() { a<int> e; }
next prev parent reply other threads:[~2020-10-11 20:25 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-11 19:58 [Bug c++/97372] New: " public at enkore dot de 2020-10-11 20:00 ` [Bug c++/97372] " public at enkore dot de 2020-10-11 20:16 ` public at enkore dot de 2020-10-11 20:25 ` public at enkore dot de [this message] 2020-10-11 20:30 ` public at enkore dot de 2020-10-12 6:35 ` rguenth at gcc dot gnu.org 2020-10-12 7:40 ` [Bug c++/97372] [8/9/10/11 Regression] ICE in Tracy 0.7.3 in template class since r8-2836-gb54d4018b17c8e7b marxin at gcc dot gnu.org 2020-10-16 12:19 ` rguenth at gcc dot gnu.org 2021-01-14 9:24 ` rguenth at gcc dot gnu.org 2021-03-12 0:37 ` 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-97372-4-i0SBkTsNsg@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).