On Mon, Apr 12, 2010 at 7:47 AM, Joel Sherrill <joel.sherr...@oarcorp.com> wrote: > On 04/12/2010 09:05 AM, Richard Guenther wrote: >> >> On Mon, Apr 12, 2010 at 4:00 PM, Joel Sherrill >> <joel.sherr...@oarcorp.com> wrote: >> >>> >>> Hi, >>> >>> I was testing i386-rtems4.10 and 225 >>> tests failed on the target because it >>> does not have any SSE flavor. It is >>> the last failures in >>> >>> http://gcc.gnu.org/ml/gcc-testresults/2010-04/msg00954.html >>> >>> FAIL: gcc.target/i386/sse-10.c execution test >>> FAIL: gcc.target/i386/sse-11.c execution test >>> ..... >>> FAIL: gcc.target/i386/sse3-movshdup.c execution test >>> FAIL: gcc.target/i386/sse3-movsldup.c execution test >>> ... >>> FAIL: gcc.target/i386/vperm-v4sf-1.c execution test >>> FAIL: gcc.target/i386/vperm-v4si-1.c execution test >>> >>> >>> A while back, some tests had run-time >>> checks added to ensure they were on a >>> CPU with the proper support. Are these >>> tests doing that or is there another >>> issue? >>> >> >> They do it via sse2-check.h and cpuid.h. Try to figure out why >> that doesn't work for your CPU (which is ...?) >> >> > > qemu with no cpu argument specified. So qemu32. > It does run OK when I change the cpu model to 486 > or pentium. > > cpu_id returns this for the qemu32 cpu model (test fails) > > a=0x633 b=0x800 c=0x1 d=0x781abfd > > this for the 486 model (test works) > > a=0x0 b=0x0 c=0x0 d=0x0 > > this for pentium (test works) > > a=0x543 b=0x800 c=0x0 d=0x8001bf > > and this for "coreduo" (test fails) > > a=0x6e8 b=0x800 c=0x9 d=0x789fbff > > Is qemu reporting that it supports SSE and not doing a good > enough job to make gcc happen? >
I think your qemu lied. It reports SSE in cpuid, but it doesn't support it. -- H.J.