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
.
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:
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
On Mon, Apr 12, 2010 at 09:47:04AM -0500, Joel Sherrill wrote:
qemu with no cpu argument specified. So qemu32.
It does run OK when I change the cpu model to 486
or pentium.
Is qemu reporting that it supports SSE and not doing a good
enough job to make gcc happen?
I think that's quite
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
On 04/12/2010 09:56 AM, Nathan Froyd wrote:
On Mon, Apr 12, 2010 at 09:47:04AM -0500, Joel Sherrill wrote:
qemu with no cpu argument specified. So qemu32.
It does run OK when I change the cpu model to 486
or pentium.
Is qemu reporting that it supports SSE and not doing a good
enough job