From: Mike Frysinger <vapier@gentoo.org>
To: Alan Modra <amodra@gmail.com>
Cc: Ian Lance Taylor <iant@google.com>, binutils@sourceware.org
Subject: Re: [PATCH 2/2] gold: enable new dtags by default
Date: Thu, 17 Jan 2013 04:09:00 -0000 [thread overview]
Message-ID: <201301162312.22951.vapier@gentoo.org> (raw)
In-Reply-To: <20130117034217.GW3244@bubble.grove.modra.org>
[-- Attachment #1: Type: Text/Plain, Size: 1066 bytes --]
On Wednesday 16 January 2013 22:42:17 Alan Modra wrote:
> On Tue, Jan 15, 2013 at 12:02:31PM -0800, Ian Lance Taylor wrote:
> > On Tue, Jan 15, 2013 at 11:35 AM, Mike Frysinger wrote:
> > > patch 1/2 doesn't change any defaults ... just adds a new flag
> >
> > Understood. I only want to add that flag to gold if it is added to
> > GNU ld. That is, I am deferring the decision about the flag to the
> > other binutils maintainers.
>
> On further thinking about this, I'd be happy with changing the
> existing flag, --enable-new-dtags, to have the behaviour proposed for
> --enable-new-dtags-only. As Mike said, the "new" dtags have been
> around for a mighty long time, and emitting both old and new tags was
> really only for backward compatibility. Is anyone running a system
> with a 14 year old glibc? If there is, do they also want the latest
> binutils?
i'm happy with that course. the new -only flag was merely to keep from rocking
the boat.
how do you feel about also enabling --enable-new-dtags by default in ld.bfd ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-17 4:09 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 7:29 [PATCH] [RFC] ld: add new --enable-new-dtags-only flag Mike Frysinger
2013-01-08 9:32 ` Alan Modra
2013-01-08 11:25 ` Mike Frysinger
2013-01-11 6:03 ` [PATCH v2] " Mike Frysinger
2013-01-11 9:22 ` John Marino
2013-01-11 16:34 ` Mike Frysinger
2013-01-12 6:30 ` [PATCH 1/2 v3] ld: add new --{dis,en}able-new-dtags-only flag Mike Frysinger
2013-01-12 6:30 ` [PATCH 2/2] gold: enable new dtags by default Mike Frysinger
2013-01-15 14:47 ` Ian Lance Taylor
2013-01-15 17:37 ` Mike Frysinger
2013-01-15 19:06 ` Ian Lance Taylor
2013-01-15 19:32 ` Mike Frysinger
2013-01-15 20:02 ` Ian Lance Taylor
2013-01-15 21:06 ` Mike Frysinger
2013-01-17 3:42 ` Alan Modra
2013-01-17 4:09 ` Mike Frysinger [this message]
2013-01-17 4:42 ` Alan Modra
2013-01-17 13:10 ` Michael Matz
2013-01-17 19:19 ` Mike Frysinger
2013-01-17 22:19 ` Alan Modra
2013-01-17 19:19 ` [PATCH 1/2 v4] ld: change --enable-new-dtags to only generate new dtags Mike Frysinger
2013-01-17 19:18 ` [PATCH 2/2 v4] gold: enable new dtags by default Mike Frysinger
2013-01-17 21:33 ` [PATCH 1/2 v4] ld: change --enable-new-dtags to only generate new dtags Alan Modra
2013-01-17 22:26 ` Mike Frysinger
2013-01-18 4:23 ` [PATCH 1/2 v5] " Mike Frysinger
2013-01-18 4:23 ` [PATCH 2/2 v5] gold: enable new dtags by default Mike Frysinger
2013-01-18 6:24 ` Ian Lance Taylor
2013-02-05 1:44 ` H.J. Lu
2013-02-05 5:43 ` Ian Lance Taylor
2013-02-05 9:39 ` Alan Modra
2013-02-05 14:19 ` Ian Lance Taylor
2013-02-05 21:50 ` Alan Modra
2013-02-06 16:24 ` H.J. Lu
2013-02-05 14:20 ` Ian Lance Taylor
2013-02-05 16:33 ` H.J. Lu
2013-02-05 21:57 ` Alan Modra
2013-02-06 8:24 ` Andreas Schwab
2013-02-06 16:37 ` H.J. Lu
2013-02-06 16:28 ` H.J. Lu
2013-02-06 21:44 ` Alan Modra
2013-02-05 16:47 ` H.J. Lu
2013-02-05 17:41 ` H.J. Lu
2013-02-20 6:15 ` Mike Frysinger
2013-02-20 17:17 ` H.J. Lu
2013-02-20 18:40 ` Mike Frysinger
2014-02-05 0:12 ` Cary Coutant
2014-02-05 2:29 ` Joseph S. Myers
2014-02-05 16:53 ` Cary Coutant
2014-02-05 17:01 ` Joseph S. Myers
2013-01-18 14:00 ` [PATCH 1/2 v5] ld: change --enable-new-dtags to only generate new dtags Alan Modra
2013-01-18 21:02 ` [PATCH] ld: enable new dtags by default for linux/gnu targets Mike Frysinger
2013-01-19 6:42 ` Alan Modra
2013-01-19 8:40 ` Andreas Schwab
2013-01-19 16:12 ` Mike Frysinger
2013-01-21 8:26 ` Mike Frysinger
2013-01-31 0:47 ` Hans-Peter Nilsson
2013-01-31 0:58 ` Hans-Peter Nilsson
2013-01-31 9:58 ` Hans-Peter Nilsson
2013-02-04 18:15 ` H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201301162312.22951.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=iant@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).