public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/63741] lm32 ICE in dwarf2out_frame_debug_expr, at dwarf2cfi.c:1677 Date: Tue, 04 Nov 2014 23:13:00 -0000 [thread overview] Message-ID: <bug-63741-4-jpi7xoZvSj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63741-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63741 Joel Sherrill <joel at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |4.9.1 --- Comment #1 from Joel Sherrill <joel at gcc dot gnu.org> --- Confirmed in lm32-rtems4.11-gcc (GCC) 4.9.2 20141028 (prerelease) But now at: $ ~/test-gcc/install-head/bin/lm32-rtems4.11-gcc -O2 -g -c /tmp/fastlz.c In file included from ../../../../../../rtems/c/src/../../cpukit/libdl/fastlz.c:113:0: ../../../../../../rtems/c/src/../../cpukit/libdl/fastlz.c: In function 'fastlz1_compress': ../../../../../../rtems/c/src/../../cpukit/libdl/fastlz.c:418:1: internal compiler error: in dwarf2out_frame_debug_expr, at dwarf2cfi.c:1675 0x52ddb0 dwarf2out_frame_debug_expr ../../gcc/gcc/dwarf2cfi.c:1675 0x52e3ac dwarf2out_frame_debug ../../gcc/gcc/dwarf2cfi.c:2043 0x52e3ac scan_insn_after ../../gcc/gcc/dwarf2cfi.c:2369 0x52fc37 scan_trace ../../gcc/gcc/dwarf2cfi.c:2526 0x530690 create_cfi_notes ../../gcc/gcc/dwarf2cfi.c:2565 0x530690 execute_dwarf2_frame ../../gcc/gcc/dwarf2cfi.c:2925 0x530690 execute ../../gcc/gcc/dwarf2cfi.c:3421 Please submit a full bug report, with preprocessed source if appropriate.
next parent reply other threads:[~2014-11-04 23:13 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-63741-4@http.gcc.gnu.org/bugzilla/> 2014-11-04 23:13 ` joel at gcc dot gnu.org [this message] 2014-11-05 15:33 ` joel at gcc dot gnu.org 2015-01-19 21:05 ` joel at gcc dot gnu.org 2015-01-20 9:40 ` ubizjak at gmail dot com 2015-01-20 18:43 ` joel at gcc dot gnu.org 2015-01-20 19:01 ` joel 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-63741-4-jpi7xoZvSj@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).