I would be happy to retest on the BeagleBone and the Raspberry Pi when a relevant build is ready.
Regards, Jerry On Fri, Jan 25, 2013 at 3:07 PM, Thomas Preud'homme <[email protected]>wrote: > Le mercredi 23 janvier 2013 22:48:02, Thomas Preud'homme a écrit : > > > > > There is a failure after > > > that, but it looks like this: > > > gcc -o libtcc_test libtcc_test.c ../libtcc.a -I. -I/var/log/tinycc > -Wall > > > -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare > > > -DTCC_TARGET_ARM -DWITHOUT_LIBTCC -DTCC_ARM_EABI -DTCC_ARM_VFP -lm > -ldl > > > ------------ libtest ------------ > > > ./libtcc_test lib_path=.. > > > Hello World! > > > fib(32) = 2178309 > > > add(32, 64) = 96 > > > cp ../include/tcclib.h . > > > gcc -o tcctest.gcc tcctest.c -I. -I. -I/var/log/tinycc -w -Wall -g -O2 > > > -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare > -DTCC_TARGET_ARM > > > -DWITHOUT_LIBTCC -DTCC_ARM_EABI -DTCC_ARM_VFP -std=gnu99 -O0 > > > -fno-omit-frame-pointer > > > ./tcctest.gcc > test.ref > > > /bin/sh: line 1: 7477 Segmentation fault ./tcctest.gcc > test.ref > > > make[1]: *** [test.ref] Error 139 > > > make[1]: Leaving directory `/var/log/tinycc/tests' > > > make: *** [test] Error 2 > > > > > > which is obviously much farther along (benchmark vs. gcc?) > > > > Indeed. Let's solve the previously mentionned bug and then we'll see for > > this one. > > This bug is my next target and then I plan to release. Hopefully it's the > same > bug which does random segfault throughout the testsuite. > > Best regards, > > Thomas > -- Interested in bats? Check out my blog at: http://www.karaokebats.com/
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
