public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "st at quanttec dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61838] ICE on Windows with ctors defined outside class definitions Date: Mon, 08 Sep 2014 19:40:00 -0000 [thread overview] Message-ID: <bug-61838-4-jYX9rGdO4O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61838-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61838 Stephan Tolksdorf <st at quanttec dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |st at quanttec dot com --- Comment #2 from Stephan Tolksdorf <st at quanttec dot com> --- This regression from 4.8 seems to have been fixed on trunk but is still present on the 4.9 branch. Could the fix be packported to 4.9? Compiling the following simple snippet with "-std=c++11" produces a segfault with 4.9: template <typename... Ts> struct A {}; struct B { B(A<int>); }; B::B(A<int>) {} cc1plus: internal compiler error: Segmentation fault 0x919b1f crash_signal ../../gcc/gcc/toplev.c:337 0x6a5ea2 analyze_functions ../../gcc/gcc/cgraphunit.c:1043 0x6a6f4f finalize_compilation_unit() ../../gcc/gcc/cgraphunit.c:2327 0x559ebb cp_write_global_declarations() ../../gcc/gcc/cp/decl2.c:4616
next prev parent reply other threads:[~2014-09-08 19:40 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-18 1:48 [Bug c++/61838] New: " lh_mouse at 126 dot com 2014-07-19 22:51 ` [Bug c++/61838] " harald at gigawatt dot nl 2014-09-08 19:40 ` st at quanttec dot com [this message] 2015-02-10 17:39 ` ktietz 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-61838-4-jYX9rGdO4O@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).