http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51251
--- Comment #1 from Joel Sherrill <joel at gcc dot gnu.org> 2011-11-21 00:55:32 UTC --- Command used to compile and link the test. /home2/joel/build/b-sparc-fortran/gcc/testsuite/gfortran/../../gfortran \ -L /users/joel/test-gcc/install-svn/sparc-rtems4.11/lib/ \ -B/home2/joel/build/b-sparc-fortran/gcc/testsuite/gfortran/../../ -B/home2/joel/build/b-sparc-fortran/sparc-rtems4.11/./libgfortran/ /users/joel/test-gcc/gcc-svn/gcc/testsuite/gfortran.dg/vect/vect-5.f90 gfortran_tg.o -O -O2 -ftree-vectorize -fno-vet-cost-model -ftree-vectorizer-verbose=4 -fdump-tree-vect-stats -mcpu=ultrasparc -mvis -B/users/joel/test-gcc/install-svn/sparc-rtems4.11/sis/lib/ -specs bsp_specs -qrtems -mcpu=cypress /home2/joel/build/b-sparc-fortran/rtems_gcc_main.o -B/home2/joel/build/b-sparc-fortran/sparc-rtems4.11/./libgfortran/.libs -L/home2/joel/build/b-sparc-fortran/sparc-rtems4.11/./libgfortran/.libs -Wl,-wrap,exit -Wl,-wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort -lm -o ./vect-5.exe 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. I added -mno-vis after the -mcpu=cypress and that let the test compile and run. Any ideas on how to deal with that? Should -mcpu=cypress turn off vis?