|
楼主 |
发表于 2004-10-3 14:13:23
|
显示全部楼层
一些说明(来自 man gcc):
-fpic
Generate position-independent code (PIC) suitable for use in a
shared library, if supported for the target machine. Such code
accesses all constant addresses through a global offset table
(GOT). The dynamic loader resolves the GOT entries when the pro-
gram starts (the dynamic loader is not part of GCC; it is part of
the operating system). If the GOT size for the linked executable
exceeds a machine-specific maximum size, you get an error message
from the linker indicating that -fpic does not work; in that case,
recompile with -fPIC instead. (These maximums are 16k on the m88k,
8k on the SPARC, and 32k on the m68k and RS/6000. The 386 has no
such limit.)
Position-independent code requires special support, and therefore
works only on certain machines. For the 386, GCC supports PIC for
System V but not for the Sun 386i. Code generated for the IBM
RS/6000 is always position-independent.
-fPIC
If supported for the target machine, emit position-independent
code, suitable for dynamic linking and avoiding any limit on the
size of the global offset table. This option makes a difference on
the m68k, m88k, and the SPARC.
Position-independent code requires special support, and therefore
works only on certain machines.
-fpie
-fPIE
These options are similar to -fpic and -fPIC, but generated posi-
tion independent code can be only linked into executables. Usually
these options are used when -pie GCC option will be used during
linking. |
|