public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/55328] New: ICE: in output_addr_table_entry, at dwarf2out.c:21780 with -gsplit-dwarf Date: Wed, 14 Nov 2012 20:41:00 -0000 [thread overview] Message-ID: <bug-55328-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55328 Bug #: 55328 Summary: ICE: in output_addr_table_entry, at dwarf2out.c:21780 with -gsplit-dwarf Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Created attachment 28687 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28687 reduced testcase Compiler output: $ gcc -O -gsplit-dwarf testcase.c testcase.c:5:1: internal compiler error: in output_addr_table_entry, at dwarf2out.c:21780 } ^ 0x709e9b output_addr_table_entry /mnt/svn/gcc-trunk/gcc/dwarf2out.c:21779 0x11d23b7 htab_traverse_noresize /mnt/svn/gcc-trunk/libiberty/hashtab.c:784 0x746329 output_addr_table /mnt/svn/gcc-trunk/gcc/dwarf2out.c:21820 0x746329 dwarf2out_finish /mnt/svn/gcc-trunk/gcc/dwarf2out.c:23528 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. Tested revisions: r193495 - crash
next reply other threads:[~2012-11-14 20:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-14 20:41 zsojka at seznam dot cz [this message] 2012-11-14 23:37 ` [Bug debug/55328] " sterling at gcc dot gnu.org 2012-11-15 0:19 ` ccoutant at gcc dot gnu.org 2013-03-05 19:27 ` ccoutant 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-55328-4@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).