Bug 34433 - Internal error while porting to PISA
Summary: Internal error while porting to PISA
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: other (show other bugs)
Version: 4.2.2
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-11 13:53 UTC by Rodrigo González Alberquilla
Modified: 2007-12-15 21:02 UTC (History)
1 user (show)

See Also:
Host: i686-pc-linux
Target: sslittle-na-sstrix
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rodrigo González Alberquilla 2007-12-11 13:53:45 UTC
Hello, I am trying to port gcc-4.2.2 to the PISA architecture, for SimplesScalar simulator. I have already created ss.h, ss.c, ss.md, ss-protos.h, ss.opt and modified the configuration scripts accordingly. I have had it configured just for c language, then I try to build it by typing

make all-gcc

It begins to compile, and then it outputs (command line + output):
*********************************************************************
 me@mymachine $ /home/rekai/opt/gcc-4.2.2/host-i686-pc-linux/gcc/xgcc -v -save-temps -B/home/rekai/opt/gcc-4.2.2/host-i6-pc-linux/gcc/ -B/home/rekai/opt/sslittle-na-sstrix/bin/ -B/home/rekai/opt/sslittle-na-sstrix/lib/ -isystem /home/rekai/opt/sslittle-na-sstrix/include -isystem /home/rekai/opt/sslittle-na-sstrix/sys-include -O2  -O2 -g -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include   -g  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../.././gcc -I../.././gcc/. -I../.././gcc/../include -I../.././gcc/../libcpp/include  -I../.././gcc/../libdecnumber -I../libdecnumber -DL_muldi3 -c ../.././gcc/libgcc2.c -o libgcc/./_muldi3.o
Reading specs from /home/rekai/opt/gcc-4.2.2/host-i686-pc-linux/gcc/specs
Target: sslittle-na-sstrix
Configured with: 
Thread model: single
gcc version 4.2.2
 /home/rekai/opt/gcc-4.2.2/host-i686-pc-linux/gcc/cc1 -E -quiet -v -I. -I. -I../.././gcc -I../.././gcc/. -I../.././gcc/../include -I../.././gcc/../libcpp/include -I../.././gcc/../libdecnumber -I../libdecnumber -iprefix /home/rekai/opt/gcc-4.2.2/host-i686-pc-linux/gcc/../lib/gcc/sslittle-na-sstrix/4.2.2/ -isystem /home/rekai/opt/gcc-4.2.2/host-i686-pc-linux/gcc/include -D__LANGUAGE_C__ -D__LANGUAGE_C -DLANGUAGE_C -DIN_GCC -DCROSS_COMPILE -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -DL_muldi3 -isystem /home/rekai/opt/sslittle-na-sstrix/include -isystem /home/rekai/opt/sslittle-na-sstrix/sys-include -isystem ./include ../.././gcc/libgcc2.c -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -fworking-directory -O2 -O2 -O2 -fpch-preprocess -o libgcc2.i
cc1: internal compiler error: in common_handle_option, at opts.c:1024
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
*************************************************************************
and as it is a precompiler error there is no temporal file output.

The native compiler used is:
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-targets=all --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.2.3 20071014 (prerelease) (Debian 4.2.2-3)

I would like to send you the config/ss folder for you to have the files. If you need these files, tell me how to send you the files.
Comment 1 Andrew Pinski 2007-12-11 17:02:33 UTC
cc1: internal compiler error: in common_handle_option, at opts.c:1024

Can't you debug this your self?
      /* If the flag was handled in a standard way, assume the lack of
         processing here is intentional.  */
      gcc_assert (cl_options[scode].flag_var);
Comment 2 Andrew Pinski 2007-12-15 21:02:28 UTC
This is not the correct location for asking for help on porting.  Ask the gcc@ list.  But you might as well run cc1 under the debugger and see why there is an assert happening.