aboutsummaryrefslogtreecommitdiff
path: root/gold/options.h
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2013-01-18 17:44:31 +0000
committerMike Frysinger <vapier@gentoo.org>2013-01-18 17:44:31 +0000
commit50701cc170a7c10a72e5ec2c7c6ed31057a31d43 (patch)
treea92ea5adcd9822faf808abe3ba4c9224dcdf1faf /gold/options.h
parentb1b00fcc619cfa409c4e244f609ab82f3a3c37d2 (diff)
downloadgdb-50701cc170a7c10a72e5ec2c7c6ed31057a31d43.zip
gdb-50701cc170a7c10a72e5ec2c7c6ed31057a31d43.tar.gz
gdb-50701cc170a7c10a72e5ec2c7c6ed31057a31d43.tar.bz2
gold: enable new dtags by default
The "new" dtags options have been around for 14+ years, and for all the targets that gold supports, these flags have always existed. So enable them by default. Having behavior be different from ld.bfd isn't new, and this behavior is the "better" one, so there shouldn't be a problem based on that. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Diffstat (limited to 'gold/options.h')
-rw-r--r--gold/options.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/gold/options.h b/gold/options.h
index 1eb2da2..9e65e8d 100644
--- a/gold/options.h
+++ b/gold/options.h
@@ -904,7 +904,7 @@ class General_options
N_("Do not page align data, do not make text readonly"),
N_("Page align data, make text readonly"));
- DEFINE_enable(new_dtags, options::EXACTLY_TWO_DASHES, '\0', false,
+ DEFINE_enable(new_dtags, options::EXACTLY_TWO_DASHES, '\0', true,
N_("Enable use of DT_RUNPATH and DT_FLAGS"),
N_("Disable use of DT_RUNPATH and DT_FLAGS"));