On Wednesday 31 January 2007 11:26:38 Ismail Dönmez wrote:
> On Tuesday 30 January 2007 18:43:52 Ian Lance Taylor wrote:
> > Ismail Dönmez <ismail@pardus.org.tr> writes:
> > > I am getting this when I try to compile gcc trunk:
> > >
> > > ../../libcpp/../include -I../../libcpp/include -march=i686 -O2 -pipe
> > > -fomit-frame-pointer -U_FORTIFY_SOURCE -fprofile-use -W -Wall
> > > -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
> > > -Wold-style-definition -Wmissing-format-attribute -pedantic
> > > -Wno-long-long -Werror -I../../libcpp -I. -I../../libcpp/../include
> > > -I../../libcpp/include -c -o files.o -MT files.o -MMD -MP -MF
> > > .deps/files.Po ../../libcpp/files.c ../../libcpp/files.c: In function
> > > 'read_name_map':
> > > ../../libcpp/files.c:1238: internal compiler error: Floating point
> > > exception Please submit a full bug report,
> > > with preprocessed source if appropriate.
> > > See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> >
> > libcpp/files.c:1238 seems to be a call to memcpy. I don't see
> > anyplace a floating point exception might come from. I've certainly
> > never seen anything like that.
>
> I think this is an hardware error
Ok its not, I tried to build on AMD64 3500+ 1GB RAM ( unlike my Centrino
laptop, totally different hardware ) and it crashes in the same exact way.
now my guess is host compiler is somehow hosed , bad news for gcc 4.2 I
guess.