On Wed, 6 Aug 2008, Joel Sherrill wrote: > Hi, > > I have just posted the first gcc test results > for arm-rtems to gcc-testresults. > C/C++: http://gcc.gnu.org/ml/gcc-testresults/2008-08/msg00608.html > Ada: http://gcc.gnu.org/ml/gcc-testresults/2008-08/msg00601.html > > There were a lot (2116) of "unexpected failures" > for C, but most (1997 by grep) appear to be because > the ep7312 is not a Neon CPU and the tests did not > even compiler. > > As with other RTEMS test configurations, we are > passing an explicit CPU model CFLAGS (-mcpu=arm7tdmi). > > Any suggestions on how this entire set of > tests can detect they don't apply?
They all use the arm_neon_ok effective target. Possibly that should check that NEON is enabled when passing -mfpu=neon -mfloat-abi=softfp (i.e. that __ARM_NEON__ is defined) rather than simply that the compiler does not give an error, if the problem is that your multilib options (passed after the options specific to the tests) disable NEON. Or if the combination is simply incompatible, possibly the compiler should be giving an error for it. -- Joseph S. Myers [EMAIL PROTECTED]
