GMP 6.0.0a on AMD A8-6600K

[tg at gmplib.org]

Kevin Buckley <kevin.m.buckley at gmail.com> writes:

  When building GMP inside the LFS chroot, the configure ends with
  
    Version:           GNU MP 6.0.0
    Host type:         piledriver-unknown-linux-gnu
    ABI:               64
    Install prefix:    /usr
    Compiler:          gcc -std=gnu99
    Static libraries:  yes
    Shared libraries:  yes
  
  and the compilation of the first test that fails
  
  /usr/src/gmp/gmp-6.0.0/tests/mpn/t-get_d
  
  shows as:
  
  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../tests     \
   -O2 -pedantic -fomit-frame-pointer -m64 -mtune=bdver2 -march=bdver2 \
   -c t-get_d.c
  
I cannot see any sort of error there.
  
  Configure (different --prefix to avoid trashing the host) ends with
  
    Version:           GNU MP 6.0.0
    Host type:         piledriver-unknown-linux-gnu
    ABI:               64
    Install prefix:    /usr/local
    Compiler:          gcc -std=gnu99
    Static libraries:  yes
    Shared libraries:  yes
  
  and the first test to fail (as above) gets built as
  
  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../tests     \
   -O2 -pedantic -fomit-frame-pointer -m64 -mtune=bdver2 -march=bdver2 \
   -c t-get_d.c
  
That doesn't look like an error message either.
  
  Configure (different --prefix to avoid trashing the host) ends with
  
    Version:           GNU MP 6.0.0
    Host type:         piledriver-unknown-linux-gnu
    ABI:               64
    Install prefix:    /usr/local
    Compiler:          gcc -std=gnu99
    Static libraries:  yes
    Shared libraries:  yes
  
  however, the first test to fail (as above) gets built as
  
  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../tests     \
   -O2 -pedantic -fomit-frame-pointer -m64 -mtune=bdver1 -march=bdver1 \
   -c t-get_d.c
  
Again, no error message.
  
  Note that the Ubuntu 12.04 box, the "bare metal host" uses these flags
  
  -mtune=bdver1 -march=bdver1
  
  whereas the CentOS 6.6 VM is using
  
  -mtune=bdver2 -march=bdver2
  
  The whole thing has sure got me beat but that last bit seems weirder
  still!
  
I don't get the point.  What is weird about those options?  The ideal
options for piledriver is bdver2, with a fallback to bdver1.

  All I know is, I can't seem to run successful tests of GMP 6.0.0a in
  three different environments, albeit with two of them "nested "
  
  Is it a bug?
  
  If it isn't, what have I missed?
  
You seem to assme that compilation command are error messages.  Or else,
you suppress some error message and leave it to us to guess what might
have happened.  We're good at aritgmetic over here, but terrible
guessers.   :-)


-- 
Torbjörn
Please encrypt, key id 0xC8601622