This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Mon, Aug 16, 2004 at 12:43:01AM +0200, Dimitry Andric wrote: > > (But that then gives me ICEs when I try to build the compiler with > > itself, aiiieee.) > > Hmm, I've seen your posts, but never encountered this before. This > needs some investigation... (I'll respond to the rest of your post later.) Some 24 hours later I think I found why bootstrapping a hardfloat gcc 3.4 on the ARM target is causing ICEs for me. If I compile a build=i686-pc-linux-gnu host=i686-pc-linux-gnu target=armeb-unknown-linux-gnu toolchain using crosstool 0.28rc32, using the standard hardfloat configuration, I end up with a toolchain that has broken float behavior. Either that, or target kernel FPU emulation is broken. On host: % cat x.c #include <stdio.h> #include <stdlib.h> int main() { float x; x = 1.0; printf("%f\n", x); return 0; } % armeb-unknown-linux-gnu-gcc -Wall -o /opt/enp2611_root/tmp/x x.c % On target: [root@enp2611 tmp]# ./x 0.000000 [root@enp2611 tmp]# If I try to print 1.1, I get "-0.000000". If I try to print 1.2, I get "2.000000". If I try to print 1.3, I get "-2.000000". And if I try to print 1.4, I get (hang on) "26815622249480124604215817416420243243587272560002206992098063765762173090970884294781200568594023450472595307446283091495952708613797907653947046282395648.000000" Maybe you have an idea off the top of your hat what's going wrong here? cheers, Lennert ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |