This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Status of m6812 target
- From: Ian Lance Taylor <iant at google dot com>
- To: Yevgeny Binder <yev at quantumcode dot net>
- Cc: gcc-help at gcc dot gnu dot org, stcarrez at nerim dot fr
- Date: Sun, 02 Jan 2011 12:28:42 -0800
- Subject: Re: Status of m6812 target
- References: <D821278A-6A07-43AC-A9D1-915F55CB5832@quantumcode.net> <mcrd3oiwdop.fsf@google.com> <ADB3FF7E-D0BC-4996-A8F8-AD701D1D528E@quantumcode.net>
Yevgeny Binder <yev@quantumcode.net> writes:
> After compiling and installing binutils-2.21, I'm trying to compile the latest stable gcc release (4.5.2) on OS X 10.6.5 with the standard developer tools, which include a binary distribution of gcc 4.2.1. I get through about 5 minutes of compilation before this happens, with 100% reproducibility:
>
> ----
> objdir/./gcc/xgcc -Bobjdir/./gcc/ -Bm6812-elf/bin/ -Bm6812-elf/lib/ -isystem m6812-elf/include -isystem m6812-elf/sys-include -g -O2 -m68hc11 -Os -mrelax -DUSE_GAS -DIN_GCC -Dinhibit_libc -g -DIN_LIBGCC2 -I. -I. -I../../.././gcc -I../../../../src/gcc-4.5.2/libgcc -I../../../../src/gcc-4.5.2/libgcc/. -I../../../../src/gcc-4.5.2/libgcc/../gcc -I../../../../src/gcc-4.5.2/libgcc/../include -DHAVE_CC_TLS -DUSE_EMUTLS -o _negdi2.o -MT _negdi2.o -MD -MP -MF _negdi2.dep -DL_negdi2 -c ../../../../src/gcc-4.5.2/libgcc/../gcc/libgcc2.c \
>
> ../../../../src/gcc-4.5.2/libgcc/../gcc/libgcc2.c: In function â__negdi2â:
> ../../../../src/gcc-4.5.2/libgcc/../gcc/libgcc2.c:76:1: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> make[4]: *** [_negdi2.o] Error 1
> make[3]: *** [multi-do] Error 1
> make[2]: *** [all-multi] Error 2
> make[1]: *** [all-target-libgcc] Error 2
> make: *** [all] Error 2
> ----
>
> I did some hunting and found that this is an instance of bug 32431, http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32431 . Apparently it's been open for over three years. Since this is a known bug, I won't file a new report, but I'm wondering if anyone would be kind enough to take another look at fixing it. From the bug tracking notes, it looks like the fix is nontrivial, at least for users unfamiliar with gcc internals (myself). I'd be happy to do testing on my end if someone figures out a solution. Thanks!
Cc'ing the listed maintainer of the m6812 target, Stephane Carrez.
Ian