Building GMP 6.0 for Ivy Bridge

Victor Shoup shoup at
Fri Oct 2 19:42:32 UTC 2015

Thanks.  Compiled and ran.
Output is "ivybridge".

But ./config.guess outputs x86_64 and that's what is is
in ./config.log, too. 

Here is the output from lscpu:

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                20
On-line CPU(s) list:   0-19
Thread(s) per core:    1
Core(s) per socket:    10
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 62
Model name:            Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
Stepping:              4
CPU MHz:               3099.906
BogoMIPS:              5605.23
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              25600K
NUMA node0 CPU(s):     0,2,4,6,8,10,12,14,16,18
NUMA node1 CPU(s):     1,3,5,7,9,11,13,15,17,19

Finally, Marc, if it is not too hard, could you find out if
setting build=ivybridge or build=coreisbr makes any difference? there a way for me to tell? I'd rather not go this whole cycle 

On Oct 2, 2015, at 9:16 AM, Marc Glisse wrote:

> On Fri, 2 Oct 2015, Victor Shoup wrote:
>> Was there some other code I was supposed to compile?
>> I just stripped out the program you indicated and tried compiling that by itself,
>> and got the undefined reference.
> Just below, you have an asm implementation of cpuid. Copy that to a .s file and compile both together.
>> Also, from the information I gave you on my system,
>> does --build=coreisbr-unknown-linux-gnu seem like
>> the right option?  Again, lscpu gives:
>> Model name:            Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
>> And that is definitely an ivy bridge.
> I already answered here I guess:
>>>> Hmm, I would have expected config.guess to return ivybridge-unknown-linux-gnu.
> (they might be equivalent though, I didn't check)
> -- 
> Marc Glisse

More information about the gmp-discuss mailing list