dockerfile指令,linux g++ 鏈接,Linux G++將64位共享庫代碼鏈接到靜態庫

 2023-10-21 阅读 24 评论 0

摘要:如果對象模塊將在共享庫中使用,則始終需要“位置獨立代碼”。它高度依賴于平臺,并且會產生一些開銷。您必須在amd64而不是x386上顯式指定它的原因只是它恰好是x86的默認值,而不是amd64。還要注意“-fpic”和“-fpic”之間的區別:dockerfile指令、-fpicGenerate position-indep

如果對象模塊將在共享庫中使用,則始終需要“位置獨立代碼”。它高度依賴于平臺,并且會產生一些開銷。

您必須在amd64而不是x386上顯式指定它的原因只是它恰好是x86的默認值,而不是amd64。

還要注意“-fpic”和“-fpic”之間的區別:

dockerfile指令、-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

linux內核源碼,(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 execu-

table exceeds a machine-specific maximum size, you get an error

cmake 靜態庫鏈接靜態庫?message from the linker indicating that -fpic does not work; in

that case, recompile with -fPIC instead. (These maximums are 8k

on the SPARC and 32k on the m68k and RS/6000. The 386 has no

such limit.)

linux移動文件命令、Position-independent code requires special support, and there

fore 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.

centos抓包?When this flag is set, the macros __pic__ and __PIC__ are defined to 1.

-fPIC

If supported for the target machine, emit position-independent

code, suitable for dynamic linking and avoiding any limit on the

vim查詢模式、size of the global offset table. This option makes a difference

on the m68k, PowerPC and SPARC.

Position-independent code requires special support, and therefore

works only on certain machines.

linux基本命令的使用?When this flag is set, the macros __pic__ and __PIC__ are defined to 2.

版权声明:本站所有资料均为网友推荐收集整理而来,仅供学习和研究交流使用。

原文链接:https://hbdhgg.com/2/158537.html

发表评论:

本站为非赢利网站,部分文章来源或改编自互联网及其他公众平台,主要目的在于分享信息,版权归原作者所有,内容仅供读者参考,如有侵权请联系我们删除!

Copyright © 2022 匯編語言學習筆記 Inc. 保留所有权利。

底部版权信息