public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/61558] [5 Regression] ICE: Segmentation fault Date: Fri, 12 Dec 2014 18:48:00 -0000 [thread overview] Message-ID: <bug-61558-4-AKfkxTkJWX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61558-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61558 --- Comment #17 from Jan Hubicka <hubicka at gcc dot gnu.org> --- OK I am testing the following patch. It just makes symtab code ready for DECL_ASSEMBLER_NAME returning NULL Index: symtab.c =================================================================== --- symtab.c (revision 218640) +++ symtab.c (working copy) @@ -168,6 +168,11 @@ symbol_table::insert_to_assembler_name_h tree name = DECL_ASSEMBLER_NAME (node->decl); + /* C++ FE can produce decls without associated assembler name and insert + them to symtab to hold section or TLS information. */ + if (!name) + return; + hashval_t hash = decl_assembler_name_hash (name); aslot = assembler_name_hash->find_slot_with_hash (name, hash, INSERT); gcc_assert (*aslot != node); @@ -209,6 +214,10 @@ symbol_table::unlink_from_assembler_name { tree name = DECL_ASSEMBLER_NAME (node->decl); symtab_node **slot; + + if (!name) + return; + hashval_t hash = decl_assembler_name_hash (name); slot = assembler_name_hash->find_slot_with_hash (name, hash, NO_INSERT);
next prev parent reply other threads:[~2014-12-12 18:48 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-19 7:41 [Bug c++/61558] New: ice in insert_to_assembler_name_hash dcb314 at hotmail dot com 2014-06-19 8:03 ` [Bug c++/61558] [4.10 Regression] ICE: Segmentation fault trippels at gcc dot gnu.org 2014-06-19 8:52 ` [Bug middle-end/61558] " trippels at gcc dot gnu.org 2014-06-25 10:47 ` trippels at gcc dot gnu.org 2014-07-12 5:18 ` trippels at gcc dot gnu.org 2014-08-26 12:28 ` [Bug middle-end/61558] [5 " trippels at gcc dot gnu.org 2014-08-29 9:05 ` trippels at gcc dot gnu.org 2014-09-08 0:44 ` hubicka at gcc dot gnu.org 2014-09-09 13:26 ` kikairoya at gmail dot com 2014-10-01 14:46 ` trippels at gcc dot gnu.org 2014-10-01 14:47 ` trippels at gcc dot gnu.org 2014-10-13 9:31 ` hubicka at gcc dot gnu.org 2014-10-13 11:58 ` hubicka at gcc dot gnu.org 2014-10-14 13:33 ` jason at gcc dot gnu.org 2014-11-19 12:44 ` dcb314 at hotmail dot com 2014-12-12 10:24 ` trippels at gcc dot gnu.org 2014-12-12 13:29 ` rguenth at gcc dot gnu.org 2014-12-12 18:48 ` hubicka at gcc dot gnu.org [this message] 2014-12-15 3:45 ` hubicka at gcc dot gnu.org 2014-12-15 4:12 ` hubicka 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-61558-4-AKfkxTkJWX@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).