;
; Er, something is wrong with your environment or your build.
;
; My guess is that you're not linking to the libgmp.so file yuo just
; compiled, but some variant installed which is chosen by means of dynamic
; libary search paths.
It's definitely using the new, fat library. I'll keep investigati
Andy Fiddaman writes:
Unfortunately fat binaries don't help here, the target binary still
executes mulx and lzcnt instructions even when on older CPUs. This is from
running GNU expr with a fat libgmp on an Ivy Bridge machine. The fat binary
version of the library was built on a more moder
On Wed, 4 Mar 2020, Torbj?rn Granlund wrote:
; GMP will include instructions for the host for which GMP is configured,
; These instructions come from asm file which GMP's configure selects, and
; from compiler generated code which results from compiler command line
; options which GMP passes.
;
GMP will include instructions for the host for which GMP is configured,
These instructions come from asm file which GMP's configure selects, and
from compiler generated code which results from compiler command line
options which GMP passes.
If you want GMP to run on older machines, configuring it
Hi,
I am part of a team that packages up libgmp as part of the OmniOS
operating system (an illumos distribution). The packages are built on a
variety of hardware but can be used on older systems. We build gmp
targetting older CPU features only but since version 6.2.0 we have seen
that the produc
