aboutsummaryrefslogtreecommitdiff
path: root/ci/test/00_setup_env_native_asan.sh
diff options
context:
space:
mode:
authorfanquake <fanquake@gmail.com>2020-02-06 14:15:43 +0800
committerfanquake <fanquake@gmail.com>2020-02-06 14:29:59 +0800
commit4d211c8da11253d39f10b56d23fc91fb29f485f5 (patch)
tree223603dc50223d23de109808029e3de10ee2b843 /ci/test/00_setup_env_native_asan.sh
parent8a56f79d491271120abc3843c46e9dda44edd308 (diff)
parentacd644b83d789a6cdfbeda19732119534d10058e (diff)
Merge #18003: build: remove --large-address-aware linker flag
acd644b83d789a6cdfbeda19732119534d10058e build: remove --large-address-aware linker flag (fanquake) Pull request description: This flag was used when building 32-bit Windows executables, which we no-longer do, and is not accepted by the linker for any of the hosts we currently build for. i.e: ```bash checking whether the linker accepts -Wl,--large-address-aware... no ``` --large-address-aware If given, the appropriate bit in the "Characteristics" field of the COFF header is set to indicate that this executable supports virtual addresses greater than 2 gigabytes. This should be used in conjunction with the /3GB or /USERVA=value megabytes switch in the "[operating systems]" section of the BOOT .INI. Otherwise, this bit has no effect. [This option is specific to PE targeted ports of the linker] You can check that the appropriate bit in the COFF header of our 64-bit Windows binaries is still be set using dumpbin. i.e: ```powershell dumpbin /headers .\bitcoind.exe FILE HEADER VALUES <snip> 26 characteristics Executable Line numbers stripped Application can handle large (>2GB) addresses ``` ACKs for top commit: laanwj: ACK acd644b83d789a6cdfbeda19732119534d10058e Tree-SHA512: 9711e07bc08e843fcefd0517091a59cb7670dd107d03623a146d03fe73054d0e64f78489490b37f4708eab2c4800037f923b9ec92e7f53c3df9a590242f52b55
Diffstat (limited to 'ci/test/00_setup_env_native_asan.sh')
0 files changed, 0 insertions, 0 deletions