On 29/05/13 22:30, William Harrington wrote:
On May 28, 2013, at 3:18 PM, William Harrington wrote:
Made it through cross-tools and all is linking well so far. Using the
x86_64 pure64 book right now.
Temp System time!
Made it past gcc 4.8.0 final system:
LAST_UPDATED: Obtained from SVN: tags/gcc_4_8_0_release revision 196953
Native configuration is x86_64-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/asan/asan_test.C -O2 AddressSanitizer_HugeMallocTest
Ident((char*)malloc(size))[-1] = 0 output pattern test, should match
is located 1 bytes to the left of 4299161600-byte
ERROR: g++.dg/abi/mangle33.C -std=c++98: error executing dg-final:
couldn't compile regular expression pattern: out of memory
UNRESOLVED: g++.dg/abi/mangle33.C -std=c++98: error executing
dg-final: couldn't compile regular expression pattern: out of memory
ERROR: g++.dg/abi/mangle33.C -std=c++11: error executing dg-final:
couldn't compile regular expression pattern: out of memory
UNRESOLVED: g++.dg/abi/mangle33.C -std=c++11: error executing
dg-final: couldn't compile regular expression pattern: out of memory
=== g++ Summary ===
# of expected passes 53784
# of unexpected failures 1
# of expected failures 290
# of unresolved testcases 2
# of unsupported tests 825
/sources/gcc-build/gcc/testsuite/g++/../../xg++ version 4.8.0 (GCC)
=== gcc tests ===
Running target unix
=== gcc Summary ===
# of expected passes 92864
# of expected failures 261
# of unsupported tests 1368
/sources/gcc-build/gcc/xgcc version 4.8.0 (GCC)
=== libatomic tests ===
Running target unix
=== libatomic Summary ===
# of expected passes 54
=== libgomp tests ===
Running target unix
=== libgomp Summary ===
# of expected passes 1259
=== libitm tests ===
Running target unix
=== libitm Summary ===
# of expected passes 26
# of expected failures 3
# of unsupported tests 1
=== libmudflap tests ===
Running target unix
FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test
ERROR: tcl error sourcing
/sources/gcc-4.8.0/libmudflap/testsuite/libmudflap.cth/cthfrags.exp.
ERROR: couldn't compile regular expression pattern: out of memory
=== libmudflap Summary ===
# of expected passes 1253
# of unexpected failures 3
=== libstdc++ tests ===
Running target unix
Compiler version: 4.8.0 (GCC)
Platform: x86_64-unknown-linux-gnu
configure flags: --prefix=/usr --libexecdir=/usr/lib --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-c99
--enable-long-long --enable-clocale=gnu --enable-languages=c,c++
--disable-multilib --disable-libstdcxx-pch --enable-cloog-backend=isl
--with-system-zlib --disable-cloog-version-check
--enable-checking=release --enable-libstdcxx-time
--disable-install-libiberty
EOF
Mail -s "Results for 4.8.0 (GCC) testsuite on
x86_64-unknown-linux-gnu" [email protected]
<mailto:[email protected]> &&
mv /sources/gcc-build/./gcc/testsuite/g++/g++.sum
/sources/gcc-build/./gcc/testsuite/g++/g++.sum.sent &&
mv /sources/gcc-build/./gcc/testsuite/gcc/gcc.sum
/sources/gcc-build/./gcc/testsuite/gcc/gcc.sum.sent &&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libatomic/testsuite/libatomic.sum
/sources/gcc-build/./x86_64-unknown-linux-gnu/libatomic/testsuite/libatomic.sum.sent
&&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.sum
/sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.sum.sent
&&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.sum
/sources/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.sum.sent
&&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.sum
/sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.sum.sent
&&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.sum
/sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.sum.sent
&&
mv /sources/gcc-build/./gcc/testsuite/g++/g++.log
/sources/gcc-build/./gcc/testsuite/g++/g++.log.sent &&
mv /sources/gcc-build/./gcc/testsuite/gcc/gcc.log
/sources/gcc-build/./gcc/testsuite/gcc/gcc.log.sent &&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libatomic/testsuite/libatomic.log
/sources/gcc-build/./x86_64-unknown-linux-gnu/libatomic/testsuite/libatomic.log.sent
&&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.log
/sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.log.sent
&&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.log
/sources/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.log.sent
&&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.log
/sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.log.sent
&&
mv
/sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.log
/sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.log.sent
&&
true
Those are the test logs as of now.
I think we can update the git book for pure64 and 32 bit systems, but
not for multilib. Multilib will be a bit of work. Why is a multilib
patch still required, anyway? Multilib has been around for a while.
You'd figure by now that it woulnd't be needed. Kind of like Python
and multilib, it's a pain in the wazoo.
Sincerely,
William Harrington
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
Hi
you can get rid of those out of stack space/memory issues by increasing
tcl stack space for regex's as they do in LFS
sed -i s/500/5000/ generic/regc_nfa.c
martin
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
