This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: What is needed when the "stage2" compiler produces an ICE?


Peter Burton <pburton at brio dot com> writes:

> What should I provide when the "stage2" compiler produces an ICE whilst
> building itself?
> stage2/xgcc -Bstage2/ -B/stage/peterb3/gcc322/tru64/alphaev6-dec-osf5.0/bin/
> -c -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H
> -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/config -I../../gcc/../include
> ../../gcc/predict.c -o predict.o
> ../../gcc/predict.c: In function `propagate_freq':
> ../../gcc/predict.c:708: Internal compiler error in @
> @, at F:537415312
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

do you happen to build gcc on Tru64 UNIX V5.0A with the bundled Compaq cc
as the bootstrap compiler?  If so, this compiler most likely miscompiles
gcc.  You should try to bootstrap with the latest version of Compaq C from

	http://h30097.www3.hp.com/dtk/compaqc_ov.html

Please note that you will need the OSF-DEV pak to be able to use that
compiler.  Another common problem seems to be lack of swap space: you may
need up to 700 MB to successfully bootstrap gcc.

Hope this helps.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]