public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Alan Modra <amodra@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
	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 13:10:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1301171409010.23146@wotan.suse.de> (raw)
In-Reply-To: <20130117044137.GX3244@bubble.grove.modra.org>

Hi,

On Thu, 17 Jan 2013, Alan Modra wrote:

> > how do you feel about also enabling --enable-new-dtags by default in 
> > ld.bfd ?
> 
> I'm not so comfortable with this.  After all, the new dtags do have 
> slightly different meaning to the old ones.  I think it would be better 
> to leave the default as is.

FWIW SUSE enabled the new dtags in our binutils package by default since, 
pfff, I think 2004/2005 or so.  Don't know about others.


Ciao,
Michael.

  reply	other threads:[~2013-01-17 13:10 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
2013-01-17  4:42                   ` Alan Modra
2013-01-17 13:10                     ` Michael Matz [this message]
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=alpine.LNX.2.00.1301171409010.23146@wotan.suse.de \
    --to=matz@suse.de \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=iant@google.com \
    --cc=vapier@gentoo.org \
    /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).