Hello. I'm now doing regular builds/tests from SVN of GCC, G++ and GNAT on FreeBSD x86_64 and publishing the build logs at:
http://gcc.coreland.ath.cx I hope to produce builds weekly. Unfortunately I can't publish the actual binaries due to space/bandwidth restrictions. While there aren't *too* many test failures currently, there appears to be a problem with the test suite in that it returns a 'failure' exit code when the test ends and I'm not sure if this is expected behaviour or not. Highlights of the first build (SVN r154276): === acats Summary === # of expected passes 2290 # of unexpected failures 31 *** FAILURES: c52103x c52104x c52104y c761007 c85005c c85006c c910002 c93004b c93004c c93004d c93005a c93005b c94001c c94002b c94002e c94002f c94002g c94007a c94007b c94008c c94008d c94020a c95040c c97203c c97303c c9a007a c9a009c c9a009g cb1010a cb1010c cb1010d === g++ Summary === # of expected passes 20986 # of unexpected failures 4 # of expected failures 150 # of unsupported tests 286 /gnat/obj/gcc/testsuite/g++/../../g++ version 4.5.0 20091118 (experimental) (GCC) === gcc Summary === # of expected passes 57515 # of unexpected failures 42 # of unexpected successes 4 # of expected failures 169 # of unsupported tests 1511 /gnat/obj/gcc/xgcc version 4.5.0 20091118 (experimental) (GCC) === gnat Summary === # of expected passes 739 # of unexpected failures 4 # of expected failures 5 === libgomp Summary === # of expected passes 1001 # of unexpected failures 2 # of unsupported tests 2 === libmudflap Summary === # of expected passes 1884 # of unexpected failures 10 === libstdc++ Summary === # of expected passes 6337 # of unexpected failures 2 # of expected failures 89 # of unsupported tests 389 Regards, M
