http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51251
--- Comment #6 from Joel Sherrill <joel at gcc dot gnu.org> 2011-11-21 12:21:26 UTC --- (In reply to comment #5) > > Hmmm... because of the way the test is compiled and the target flags are > > added, > > there is ... "-mcpu=ultrasparc -mvis" and then later on the command line > > "-mcpu=cypress". I wonder what that results in other than a mess. > > Whoever automatically adds -mcpu=cypress without checking whether there isn't > already a -mcpu switch specified by the user is the culprit. The board in question is really a V7 and that is the proper cpu selection. It is added by the test framework in a dejagnu board file. We have seen this before on arm and powerpc targets. In those cases, the tests or scripts had something added to them. Janice Johnson tinkered with the testsuite to address a similar failure on PowerPC. I found this message in the thread. http://lists.gnu.org/archive/html/dejagnu/2008-12/msg00012.html The issue is that when running on real hardware, you can't use arbitrary cpu flags and expect it to work. And it is wrong to say xfail on sparc-rtems because they could work on another board running rtems. Just not this one.
