public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55381] [4.8 Regression]: build fails on cris-elf building libgfortran with host-gcc-4.4, ICE compiling matmul_i1.c
Date: Tue, 20 Nov 2012 13:02:00 -0000 [thread overview]
Message-ID: <bug-55381-4-WcxqMpHXjH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55381-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55381
--- Comment #7 from Andreas Schwab <schwab@linux-m68k.org> 2012-11-20 13:01:31 UTC ---
Also broken on ia64 with gcc 4.3.2.
/usr/local/gcc/test/Build/./gcc/xgcc -B/usr/local/gcc/test/Build/./gcc/
-B/usr/ia64-suse-linux/bin/ -B/usr/ia64-suse-linux/lib/ -isystem
/usr/ia64-suse-linux/include -isystem /usr/ia64-suse-linux/sys-include -O2
-g -O2 -O2 -g -DIN_GCC -DUSE_LIBUNWIND_EXCEPTIONS -W -Wall -Wwrite-strings
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -fPIC -DUSE_GAS_SYMVER -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector -fPIC -DUSE_GAS_SYMVER -I. -I. -I../.././gcc
-I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../gcc
-I../../../libgcc/../include -DHAVE_CC_TLS -o _mulvdi3.o -MT _mulvdi3.o -MD
-MP -MF _mulvdi3.dep -DL_mulvdi3 -c ../../../libgcc/libgcc2.c
-fvisibility=hidden -DHIDE_EXPORTS
../../../libgcc/libgcc2.c: In function ‘__mulvti3’:
../../../libgcc/libgcc2.c:397:1: internal compiler error: Segmentation fault
}
^
0x40000000008bc6cf crash_signal
../../gcc/toplev.c:334
0x4000000000cb49bf vec<rtx_def*, va_stack, vl_ptr>::reserve(unsigned int, bool)
../../gcc/vec.h:1443
0x4000000000cb49bf vec<rtx_def*, va_stack, vl_ptr>::safe_push(rtx_def* const&)
../../gcc/vec.h:1540
0x4000000000cb49bf values_to_stack
../../gcc/var-tracking.c:8585
0x4000000001083dcf htab_traverse_noresize
../../libiberty/hashtab.c:784
0x4000000000cabdbf process_changed_values
../../gcc/var-tracking.c:8704
0x4000000000cac1bf emit_notes_for_changes
../../gcc/var-tracking.c:8743
0x4000000000cadaaf emit_notes_for_differences
../../gcc/var-tracking.c:8863
0x4000000000cadaaf vt_emit_notes
../../gcc/var-tracking.c:9238
0x4000000000cb476f variable_tracking_main_1
../../gcc/var-tracking.c:10066
0x4000000000cb476f variable_tracking_main()
../../gcc/var-tracking.c:10080
0x4000000000d0254f ia64_reorg
../../gcc/config/ia64/ia64.c:9798
0x40000000007fd05f rest_of_handle_machine_reorg
../../gcc/reorg.c:4152
next prev parent reply other threads:[~2012-11-20 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 16:53 [Bug middle-end/55381] New: " hp at gcc dot gnu.org
2012-11-18 17:04 ` [Bug middle-end/55381] " hp at gcc dot gnu.org
2012-11-18 19:48 ` hp at gcc dot gnu.org
2012-11-18 20:17 ` hp at gcc dot gnu.org
2012-11-19 5:46 ` venkataramanan.kumar at amd dot com
2012-11-19 17:50 ` pthaugen at gcc dot gnu.org
2012-11-19 22:08 ` bergner at gcc dot gnu.org
2012-11-20 13:02 ` schwab@linux-m68k.org [this message]
2012-11-20 16:51 ` dnovillo at gcc dot gnu.org
2012-11-20 18:12 ` hp at gcc dot gnu.org
2012-11-25 15:55 ` rguenth at gcc dot gnu.org
2012-11-25 21:01 ` hp 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-55381-4-WcxqMpHXjH@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: link
Be 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).