Thank you. I will rerun the tests on this target overnight
with this change along with disabling profiling tests
for *-*-rtems*.
It looks like the wheat and chafe are separating a bit. :)
--joel
Uros Bizjak wrote:
Joel Sherrill wrote:
This is with the Fedora 8 qemu 0.90 RPM. There was a
Joel Sherrill wrote:
This is with the Fedora 8 qemu 0.90 RPM. There was a 0.91
release in January and the ChangeLog mentions a new cpu model
command line option. It looks like it might be better although
another command line I was using broke.
Just to be sure this looks OK in qemu 0.9.1, her
Uros Bizjak wrote:
Joel Sherrill wrote:
I hacked on that test program to get the attached
program. I ran it multiple times on qemu.
ext=0x0 sig=0x756e6547
0x781abfd YES on SSE2
I am now printing the return value from __get_cpuid_max()
ext=0x0 sig=0x756e6547 returned=0x2
0
Joel Sherrill wrote:
I hacked on that test program to get the attached
program. I ran it multiple times on qemu.
ext=0x0 sig=0x756e6547
0x781abfd YES on SSE2
I am now printing the return value from __get_cpuid_max()
ext=0x0 sig=0x756e6547 returned=0x2
0x781abfd YES on SSE2
Isn't
Uros Bizjak wrote:
On Thu, Mar 13, 2008 at 2:35 PM, Joel Sherrill
<[EMAIL PROTECTED]> wrote:
I hacked on that test program to get the attached
program. I ran it multiple times on qemu.
ext=0x0 sig=0x756e6547
0x781abfd YES on SSE2
I am now printing the return value from __get_cpu
On Thu, Mar 13, 2008 at 2:35 PM, Joel Sherrill
<[EMAIL PROTECTED]> wrote:
> I hacked on that test program to get the attached
> program. I ran it multiple times on qemu.
>
> ext=0x0 sig=0x756e6547
> 0x781abfd YES on SSE2
>
> I ran the same program natively and got this:
>
> ext=0x0 sig=0x75
