LAST_UPDATED: Fri Jan 9 01:21:29 UTC 2009 (revision 143198) $ ../trunk/configure --with-arch=native --disable-java-awt --without-x --enable-__cxa_atexit --disable-libgomp --disable-static --enable-languages=c,c++,java --disable-fixed-point --enable-checking=release --with-gmp=/home/daney/mp --with-mpfr=/home/daney/mp --disable-libmudflap --disable-multilib
As noted in these test results: http://gcc.gnu.org/ml/gcc-testresults/2009-01/msg01307.html We have FAIL: gcc.target/mips/dpaq_sa_l_w.c (test for excess errors) Here is the log of the failure: Executing on host: /home/daney/gccsvn/trunk-build/gcc/xgcc -B/home/daney/gccsvn/trunk-build/gcc/ /home/daney/gccsvn/trunk/gcc/testsuite/\ gcc.target/mips/dpaq_sa_l_w.c -DNOMIPS16=__attribute__((nomips16)) -mabi=32 -mips32r2 -mgp32 -O2 -mdsp -S -o dpaq_sa_l_w.s (timeou\ t = 300) /home/daney/gccsvn/trunk/gcc/testsuite/gcc.target/mips/dpaq_sa_l_w.c:5: error: fixed-point types not supported for this target /home/daney/gccsvn/trunk/gcc/testsuite/gcc.target/mips/dpaq_sa_l_w.c:6: error: fixed-point types not supported for this target . . . The native CPU is an R5000 My untested hypothesis is that configuring with --with-arch=native has incorrect interaction with -m* from the gcc command line. -- Summary: Incorrect interaction between --with-arch=native and - mARCH Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: daney at gcc dot gnu dot org GCC build triplet: mips64-unknown-linux-gnu GCC host triplet: mips64-unknown-linux-gnu GCC target triplet: mips64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38864
