Bug 20518 - configure test FAILS on 3DNOWEXT intrinsics on amd64
Summary: configure test FAILS on 3DNOWEXT intrinsics on amd64
Status: NEW
Alias: None
Product: liboil
Classification: Unclassified
Component: unknown (show other bugs)
Version: unspecified
Hardware: Other All
: low trivial
Assignee: David Schleef
QA Contact: David Schleef
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-06 19:27 UTC by Gary Hunt
Modified: 2009-03-09 16:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Gary Hunt 2009-03-06 19:27:15 UTC
test uses a compile to gcc with march=athlon, which fails..
CPU you selected does not support x86-64 instruction set.
Comment 1 David Schleef 2009-03-07 10:33:46 UTC
Where did you get this error?
Comment 2 Gary Hunt 2009-03-09 16:14:43 UTC
(In reply to comment #0)
> test uses a compile to gcc with march=athlon, which fails..
> CPU you selected does not support x86-64 instruction set.
> 

During configure...

checking to see if compiler understands -Wall... yes
checking to see if compiler understands -Werror... yes
checking if compiler supports MMX intrinsics... yes
checking if compiler supports SSE intrinsics... yes
checking if compiler supports SSE2 intrinsics... yes
checking if compiler supports SSE3 intrinsics... yes
checking if compiler supports 3DNOW intrinsics... yes
checking if compiler supports 3DNOWEXT intrinsics... no
checking if compiler supports ALTIVEC intrinsics... no
checking if compiler supports 'pmaddubsw %%mm0, %%mm0' asm instruction... yes
configure: creating ./config.status

configure log shows CPU you selected does not support x86-64 instruction set.
Comment 3 Gary Hunt 2009-03-09 16:28:46 UTC
er during test for 3DNOWEXT 
Comment 4 David Schleef 2009-03-09 16:46:20 UTC
I get it now.

Liboil doesn't use 3dnow intrinsics anywhere, so fixing this is moot.  I'll leave the bug open, though.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.