GNU多精度算术库GMP手册6.3.0版

软件工程

性能优化

需积分: 1 65 浏览量更新于2024-06-17 收藏 824KB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

10 GNU MP 6.3.0

gcc -mabi=32

cc -32

‘ABI=n32’ The n32 ABI is 32-bit pointers and integers, but with a 64-bit limb

using a long long. Applications must be compiled with

gcc -mabi=n32

cc -n32

‘ABI=64’ The 64-bit ABI is 64-bit pointers and integers. Applications must be

compiled with

gcc -mabi=64

cc -64

Note that MIPS GNU/Linux, as of kernel version 2.2, doesn’t have the necessary

support for n32 or 64 and so only gets a 32-bit limb and the MIPS 2 code.

PowerPC 64 (‘powerpc64’, ‘powerpc620’, ‘powerpc630’, ‘powerpc970’, ‘power4’, ‘power5’)

‘ABI=mode64’

The AIX 64 ABI uses 64-bit limbs and pointers and is the default on

PowerPC 64 ‘*-*-aix*’ systems. Applications must be compiled with

gcc -maix64

xlc -q64

On 64-bit GNU/Linux, BSD, and Mac OS X/Darwin systems, the ap-

plications must be compiled with

gcc -m64

‘ABI=mode32’

The ‘mode32’ ABI uses a 64-bit long long limb but with the chip still in

32-bit mode and using 32-bit calling conventions. This is the default for

systems where the true 64-bit ABI is unavailable. No special compiler

options are typically needed for applications. This ABI is not available

under AIX.

‘ABI=32’ This is the basic 32-bit PowerPC ABI, with a 32-bit limb. No special

compiler options are needed for applications.

GMP’s speed is greatest for the ‘mode64’ ABI, the ‘mode32’ ABI is 2nd best. In

‘ABI=32’ only the 32-bit ISA is used and this doesn’t make full use of a 64-bit chip.

Sparc V9 (‘sparc64’, ‘sparcv9’, ‘ultrasparc*’)

‘ABI=64’ The 64-bit V9 ABI is available on the various BSD sparc64 ports, recent

versions of Sparc64 GNU/Linux, and Solaris 2.7 and up (when the kernel

is in 64-bit mode). GCC 3.2 or higher, or Sun cc is required. On

GNU/Linux, depending on the default gcc mode, applications must be

compiled with

gcc -m64

On Solaris applications must be compiled with

gcc -m64 -mptr64 -Wa,-xarch=v9 -mcpu=v9

cc -xarch=v9

On the BSD sparc64 systems no special options are required, since 64-

bits is the only ABI available.

‘ABI=32’ For the basic 32-bit ABI, GMP still uses as much of the V9 ISA as it

can. In the Sun documentation this combination is known as “v8plus”.

Chapter 2: Installing GMP 11

On GNU/Linux, depending on the default gcc mode, applications may

need to be compiled with

gcc -m32

On Solaris, no special compiler options are required for applications,

though using something like the following is recommended. (gcc 2.8

and earlier only support ‘-mv8’ though.)

gcc -mv8plus

cc -xarch=v8plus

GMP speed is greatest in ‘ABI=64’, so it’s the default where available. The speed

is partly because there are extra registers available and partly because 64-bits is

considered the more important case and has therefore had better code written for

it.

Don’t be confused by the names of the ‘-m’ and ‘-x’ compiler options, they’re called

‘arch’ but eﬀectively control both ABI and ISA.

On Solaris 2.6 and earlier, only ‘ABI=32’ is available since the kernel doesn’t save

all registers.

On Solaris 2.7 with the kernel in 32-bit mode, a normal native build will reject

‘ABI=64’ because the resulting executables won’t run. ‘ABI=64’ can still be built if

desired by making it look like a cross-compile, for example

./configure --build=none --host=sparcv9-sun-solaris2.7 ABI=64

2.3 Notes for Package Builds

GMP should present no great diﬃculties for packaging in a binary distribution.

Libtool is used to build the library and ‘-version-info’ is set appropriately, having started

from ‘3:0:0’ in GMP 3.0 (see Section “Library interface versions” in GNU Libtool).

The GMP 4 series will be upwardly binary compatible in each release and will be upwardly

binary compatible with all of the GMP 3 series. Additional function interfaces may be added

in each release, so on systems where libtool versioning is not fully checked by the loader an

auxiliary mechanism may be needed to express that a dynamic linked application depends on a

new enough GMP.

An auxiliary mechanism may also be needed to express that libgmpxx.la (from --enable-cxx,

see Section 2.1 [Build Options], page 3) requires libgmp.la from the same GMP version, since

this is not done by the libtool versioning, nor otherwise. A mismatch will result in unresolved

symbols from the linker, or perhaps the loader.

When building a package for a CPU family, care should be taken to use ‘--host’ (or ‘--build’)

to choose the least common denominator among the CPUs which might use the package. For

example this might mean plain ‘sparc’ (meaning V7) for SPARCs.

For x86s, --enable-fat sets things up for a fat binary build, making a runtime selection of

optimized low level routines. This is a good choice for packaging to run on a range of x86 chips.

Users who care about speed will want GMP built for their exact CPU type, to make best use

of the available optimizations. Providing a way to suitably rebuild a package may be useful.

This could be as simple as making it possible for a user to omit ‘--build’ (and ‘--host’) so

‘./config.guess’ will detect the CPU. But a way to manually specify a ‘--build’ will be

wanted for systems where ‘./config.guess’ is inexact.

On systems with multiple ABIs, a packaged build will need to decide which among the choices

is to be provided, see Section 2.2 [ABI and ISA], page 8. A given run of ‘./configure’ etc will

12 GNU MP 6.3.0

only build one ABI. If a second ABI is also required then a second run of ‘./configure’ etc

must be made, starting from a clean directory tree (‘make distclean’).

As noted under “ABI and ISA”, currently no attempt is made to follow system conventions

for install locations that vary with ABI, such as /usr/lib/sparcv9 for ‘ABI=64’ as opposed to

/usr/lib for ‘ABI=32’. A package build can override ‘libdir’ and other standard variables as

necessary.

Note that gmp.h is a generated ﬁle, and will be architecture and ABI dependent. When attempt-

ing to install two ABIs simultaneously it will be important that an application compile gets the

correct gmp.h for its desired ABI. If compiler include paths don’t vary with ABI options then

it might be necessary to create a /usr/include/gmp.h which tests preprocessor symbols and

chooses the correct actual gmp.h.

2.4 Notes for Particular Systems

AIX 3 and 4

On systems ‘*-*-aix[34]*’ shared libraries are disabled by default, since some

versions of the native ar fail on the convenience libraries used. A shared build can

be attempted with

./configure --enable-shared --disable-static

Note that the ‘--disable-static’ is necessary because in a shared build libtool

makes libgmp.a a symlink to libgmp.so, apparently for the beneﬁt of old versions

of ld which only recognise .a, but unfortunately this is done even if a fully functional

ld is available.

ARM On systems ‘arm*-*-*’, versions of GCC up to and including 2.95.3 have a bug in

unsigned division, giving wrong results for some operands. GMP ‘./configure’ will

demand GCC 2.95.4 or later.

Compaq C++

Compaq C++ on OSF 5.1 has two ﬂavours of iostream, a standard one and an old

pre-standard one (see ‘man iostream_intro’). GMP can only use the standard one,

which unfortunately is not the default but must be selected by deﬁning __USE_STD_

IOSTREAM. Conﬁgure with for instance

./configure --enable-cxx CPPFLAGS=-D__USE_STD_IOSTREAM

Floating Point Mode

On some systems, the hardware ﬂoating point has a control mode which can set

all operations to be done in a particular precision, for instance single, double or

extended on x86 systems (x87 ﬂoating point). The GMP functions involving a

double cannot be expected to operate to their full precision when the hardware is

in single precision mode. Of course this aﬀects all code, including application code,

not just GMP.

FreeBSD 7.x, 8.x, 9.0, 9.1, 9.2

m4 in these releases of FreeBSD has an eval function which ignores its 2nd and 3rd

arguments, which makes it unsuitable for .asm ﬁle processing. ‘./configure’ will

detect the problem and either abort or choose another m4 in the PATH. The bug

is ﬁxed in FreeBSD 9.3 and 10.0, so either upgrade or use GNU m4. Note that

the FreeBSD package system installs GNU m4 under the name ‘gm4’, which GMP

cannot guess.

FreeBSD 7.x, 8.x, 9.x

GMP releases starting with 6.0 do not support ‘ABI=32’ on FreeBSD/amd64 prior to

release 10.0 of the system. The cause is a broken limits.h, which GMP no longer

works around.

Chapter 2: Installing GMP 13

MS-DOS and MS Windows

On an MS-DOS system DJGPP can be used to build GMP, and on an MS Windows

system Cygwin, DJGPP and MINGW can be used. All three are excellent ports of

GCC and the various GNU tools.

https://www.cygwin.com/

http://www.delorie.com/djgpp/

http://www.mingw.org/

Microsoft also publishes an Interix “Services for Unix” which can be used to build

GMP on Windows (with a normal ‘./configure’), but it’s not free software.

MS Windows DLLs

On systems ‘*-*-cygwin*’, ‘*-*-mingw*’ and ‘*-*-pw32*’ by default GMP builds

only a static library, but a DLL can be built instead using

./configure --disable-static --enable-shared

Static and DLL libraries can’t both be built, since certain export directives in gmp.h

must be diﬀerent.

A MINGW DLL build of GMP can be used with Microsoft C. Libtool doesn’t install

a .lib format import library, but it can be created with MS lib as follows, and

copied to the install directory. Similarly for libmp and libgmpxx.

cd .libs

lib /def:libgmp-3.dll.def /out:libgmp-3.lib

MINGW uses the C runtime library ‘msvcrt.dll’ for I/O, so applications wanting

to use the GMP I/O routines must be compiled with ‘cl /MD’ to do the same. If

one of the other C runtime library choices provided by MS C is desired then the

suggestion is to use the GMP string functions and conﬁne I/O to the application.

Motorola 68k CPU Types

‘m68k’ is taken to mean 68000. ‘m68020’ or higher will give a performance boost on

applicable CPUs. ‘m68360’ can be used for CPU32 series chips. ‘m68302’ can be

used for “Dragonball” series chips, though this is merely a synonym for ‘m68000’.

NetBSD 5.x

m4 in these releases of NetBSD has an eval function which ignores its 2nd and 3rd

arguments, which makes it unsuitable for .asm ﬁle processing. ‘./configure’ will

detect the problem and either abort or choose another m4 in the PATH. The bug

is ﬁxed in NetBSD 6, so either upgrade or use GNU m4. Note that the NetBSD

package system installs GNU m4 under the name ‘gm4’, which GMP cannot guess.

OpenBSD 2.6

m4 in this release of OpenBSD has a bug in eval that makes it unsuitable for .asm

ﬁle processing. ‘./configure’ will detect the problem and either abort or choose

another m4 in the PATH. The bug is ﬁxed in OpenBSD 2.7, so either upgrade or use

GNU m4.

Power CPU Types

In GMP, CPU types ‘power*’ and ‘powerpc*’ will each use instructions not available

on the other, so it’s important to choose the right one for the CPU that will be used.

Currently GMP has no assembly code support for using just the common instruction

subset. To get executables that run on both, the current suggestion is to use the

generic C code (--disable-assembly), possibly with appropriate compiler options

(like ‘-mcpu=common’ for gcc). CPU ‘rs6000’ (which is not a CPU but a family of

workstations) is accepted by config.sub, but is currently equivalent to --disable-

assembly.

14 GNU MP 6.3.0

Sparc CPU Types

‘sparcv8’ or ‘supersparc’ on relevant systems will give a signiﬁcant performance

increase over the V7 code selected by plain ‘sparc’.

Sparc App Regs

The GMP assembly code for both 32-bit and 64-bit Sparc clobbers the “application

registers” g2, g3 and g4, the same way that the GCC default ‘-mapp-regs’ does

(see Section “SPARC Options” in Using the GNU Compiler Collection (GCC)).

This makes that code unsuitable for use with the special V9 ‘-mcmodel=embmedany’

(which uses g4 as a data segment pointer), and for applications wanting to use those

registers for special purposes. In these cases the only suggestion currently is to build

GMP with --disable-assembly to avoid the assembly code.

SunOS 4 /usr/bin/m4 lacks various features needed to process .asm ﬁles, and instead

‘./configure’ will automatically use /usr/5bin/m4, which we believe is always

available (if not then use GNU m4).

x86 CPU Types

‘i586’, ‘pentium’ or ‘pentiummmx’ code is good for its intended P5 Pentium chips,

but quite slow when run on Intel P6 class chips (PPro, P-II, P-III). ‘i386’ is a

better choice when making binaries that must run on both.

x86 MMX and SSE2 Code

If the CPU selected has MMX code but the assembler doesn’t support it, a warning

is given and non-MMX code is used instead. This will be an inferior build, since the

MMX code that’s present is there because it’s faster than the corresponding plain

integer code. The same applies to SSE2.

Old versions of ‘gas’ don’t support MMX instructions, in particular version 1.92.3

that comes with FreeBSD 2.2.8 or the more recent OpenBSD 3.1 doesn’t.

Solaris 2.6 and 2.7 as generate incorrect object code for register to register movq

instructions, and so can’t be used for MMX code. Install a recent gas if MMX code

is wanted on these systems.

2.5 Known Build Problems

You might ﬁnd more up-to-date information at https://gmplib.org/.

Compiler link options

The version of libtool currently in use rather aggressively strips compiler options

when linking a shared library. This will hopefully be relaxed in the future, but for

now if this is a problem the suggestion is to create a little script to hide them, and

for instance conﬁgure with

./configure CC=gcc-with-my-options

DJGPP (‘*-*-msdosdjgpp*’)

The DJGPP port of bash 2.03 is unable to run the ‘configure’ script, it exits

silently, having died writing a preamble to config.log. Use bash 2.04 or higher.

‘make all’ was found to run out of memory during the ﬁnal libgmp.la link on one

system tested, despite having 64MiB available. Running ‘make libgmp.la’ directly

helped, perhaps recursing into the various subdirectories uses up memory.

GNU binutils strip prior to 2.12

strip from GNU binutils 2.11 and earlier should not be used on the static libraries

libgmp.a and libmp.a since it will discard all but the last of multiple archive mem-

bers with the same name, like the three versions of init.o in libgmp.a. Binutils

2.12 or higher can be used successfully.

剩余151页未读，继续阅读

程序员Chino的日记

粉丝: 3583
资源: 5万+

GNU多精度算术库GMP手册6.3.0版

elasticsearch-analysis-ik-6.3.0.zip

en.stm32cubemx-win_v6-3-0_v6.3.0.zip

gcc-core-6.3.0-1-mingw32-bin.tar.xz

gmp-6.3.0.tar.xz

gmp-6.3.0.tar.gz

gmp-6.3.0.tar.bz2

sublime-robot-framework-assistant-st3-6.3.0.zip

hbase-client-2.1.0-cdh6.3.0.jar

drools-core-6.3.0.CR2.jar

drools-core-6.3.0.Final.jar

drools-core-6.3.0.CR1.jar

drools-core-6.3.0.Beta2.jar

drools-core-6.3.0.Beta1.jar

Postman-win64-6.3.0.zip

parent-join-client-6.3.0.jar中文-英文对照文档.zip

rank-eval-client-6.3.0.jar中文-英文对照文档.zip

lang-mustache-client-6.3.0.jar中文-英文对照文档.zip

elasticsearch-rest-client-6.3.0.jar中文-英文对照文档.zip

elasticsearch-secure-sm-6.3.0.jar中文-英文对照文档.zip

最新资源