In the svn branch x86_64-cpuid is my attempt at re-organizing the x86_64
processors.
The file cpuid.c is now the only place where detection takes place , before we
had config.guess and the two fat.c , they now just #inlcude "cpuid.c"
cpuid.c returns the microarchitecture of the processor only , no consideration
of what code will be run.
in 64bit mode we have
x86_64(default) core2 penryn nehalem atom netburst netburstlahf k8 k10
in 32bit mode we have
i486(default) pentium pentiummmx pentiumpro pentium2 pentium3 core pentium4
prescott k5 k6 k62 k63 athlon viac3 viac32 core2 penryn nehalem atom k8 k10
I've not changed the x86 CFLAGS or asm path order for static/fat ( I hope)
for non-fat builds this is the asm path search order
x86_64-*-*)
path_64="x86_64" ;;
netburst-*-*)
path_64="x86_64/netburst x86_64" ;;
netburstlahf-*-*)
path_64="x86_64/netburst/netburstlahf x86_64/netburst x86_64" ;;
k8-*-*)
path_64="x86_64/k8 x86_64" ;;
k10-*-*)
path_64="x86_64/k8/k10 x86_64/k8 x86_64" ;;
core2-*-*)
path_64="x86_64/core2 x86_64" ;;
penryn-*-*)
path_64="x86_64/core2/penryn x86_64/core2 x86_64" ;;
nehalem-*-*)
path_64="x86_64/nehalem x86_64" ;;
atom-*-*)
path_64="x86_64/atom x86_64" ;;
there is a similar one in configure.in for 64bit cpu in 32bit OS
and a similar fat path search order in fat.c
I've tested on a few machines , and it all appears to work. What I will do is
fake each cpu and test the paths that it uses.
Jason
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-devel@googlegroups.com
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
