public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <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: Sat, 19 Jul 2014 22:51:00 -0000 [thread overview] Message-ID: <bug-61838-4-Wvrrc2rIaX@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 Harald van Dijk <harald at gigawatt dot nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |harald at gigawatt dot nl --- Comment #1 from Harald van Dijk <harald at gigawatt dot nl> --- Not specific to Windows. On x86_64-pc-linux-gnu, both 4.9.1 and master as of today ICE. It works from 4.4 to 4.8. cc1plus: internal compiler error: Segmentation fault 0xbbc02f crash_signal ../../gcc/gcc/toplev.c:337 0x880df5 analyze_functions ../../gcc/gcc/cgraphunit.c:1054 0x88273f finalize_compilation_unit() ../../gcc/gcc/cgraphunit.c:2338 0x671c70 cp_write_global_declarations() ../../gcc/gcc/cp/decl2.c:4684 /* If decl is a clone of an abstract function, mark that abstract function so that we don't release its body. The DECL_INITIAL() of that abstract function declaration will be later needed to output debug info. */ if (DECL_ABSTRACT_ORIGIN (decl)) { struct cgraph_node *origin_node = cgraph_get_node (DECL_ABSTRACT_ORIGIN (decl)); 1054 origin_node->used_as_abstract_origin = true; }
next prev parent reply other threads:[~2014-07-19 22:51 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 ` harald at gigawatt dot nl [this message] 2014-09-08 19:40 ` [Bug c++/61838] " st at quanttec dot com 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-Wvrrc2rIaX@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).