diff options
author | Tom de Vries <tdevries@suse.de> | 2021-09-24 16:56:50 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2021-09-24 16:56:50 +0200 |
commit | 66484acafd396ecb9bffd9f00ff3c37aec549c83 (patch) | |
tree | 5f207c63b19f75b667ad862a2abe2805f98dc899 /gdb/testsuite/lib/dwarf.exp | |
parent | 85a0bae983fc3d4fee7f1e64ec002dcfc873f966 (diff) | |
download | gdb-66484acafd396ecb9bffd9f00ff3c37aec549c83.zip gdb-66484acafd396ecb9bffd9f00ff3c37aec549c83.tar.gz gdb-66484acafd396ecb9bffd9f00ff3c37aec549c83.tar.bz2 |
[gdb/testsuite] Use pie instead of -fpie/-pie
I noticed two test-cases where -fpie is used. Using the canonical pie option
will usually get one -fPIE instead.
That choice is justified here in gdb_compile:
...
# For safety, use fPIE rather than fpie. On AArch64, m68k, PowerPC
# and SPARC, fpie can cause compile errors due to the GOT exceeding
# a maximum size. On other architectures the two flags are
# identical (see the GCC manual). Note Debian9 and Ubuntu16.10
# onwards default GCC to using fPIE. If you do require fpie, then
# it can be set using the pie_flag.
set flag "additional_flags=-fPIE"
...
There is no indication that using -fpie rather than -fPIE is on purpose, so
use pie instead.
Tested on x86_64-linux.
Diffstat (limited to 'gdb/testsuite/lib/dwarf.exp')
0 files changed, 0 insertions, 0 deletions