From: Ian Lance Taylor <iant@google.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Paolo Bonzini <bonzini@gnu.org>,
Matthias Klose <doko@ubuntu.com>,
gcc-patches@sourceware.org, satorux@google.com,
aoliva@redhat.com, dj@redhat.com, neroden@gcc.gnu.org,
Ralf.Wildenhues@gmx.de
Subject: Re: [patch] make default linker --hash-style configurable option
Date: Tue, 10 May 2011 15:00:00 -0000 [thread overview]
Message-ID: <mcrliyemz5n.fsf@coign.corp.google.com> (raw)
In-Reply-To: <BANLkTima9JKAZOWmgq=dK0SCitoeO0FJLA@mail.gmail.com> (Richard Guenther's message of "Tue, 10 May 2011 10:55:06 +0200")
Richard Guenther <richard.guenther@gmail.com> writes:
> On Mon, May 9, 2011 at 7:11 PM, Paul Pluzhnikov <ppluzhnikov@google.com> wrote:
>> On Mon, May 9, 2011 at 9:51 AM, Joseph S. Myers <joseph@codesourcery.com> wrote:
>>> On Mon, 9 May 2011, Paolo Bonzini wrote:
>>>
>>>> Uhm, so we deadlocked, I thought the other way. I cannot really
>>>> express any opinion about the desirability of the feature, but the
>>>> configure syntax is certainly okay with me, and I gather from the
>>>> thread that you are fine with that as well.
>>>
>>> Given the build system changes, the gcc.c changes are OK.
>>
>> Ok for trunk then?
>>
>> I'll wait till tomorrow in case someone has additional comments on the
>> desirability part.
>
> I wonder why this is a GCC specific patch and not a linker patch. Why
> not change the linker(s) to accept such configure option that changes its
> default behavior?
It is traditionally gcc which tells the linker what to do. E.g., Fedora
has patched gcc to pass --hash-style=gnu to the linker.
> Otherwise if people link with ld they suddenly get different hash-style.
> That looks wrong to me.
That turns out not to be the case. Both gold and GNU ld accept the same
set of --hash-style options.
Ian
next prev parent reply other threads:[~2011-05-10 14:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 18:17 Paul Pluzhnikov
2011-04-04 18:22 ` Rainer Orth
2011-04-04 18:26 ` Ian Lance Taylor
2011-04-04 22:53 ` Matthias Klose
2011-04-05 0:01 ` Joseph S. Myers
2011-04-11 18:01 ` Paul Pluzhnikov
2011-04-18 17:20 ` Paul Pluzhnikov
2011-04-25 17:03 ` Paul Pluzhnikov
2011-05-02 14:23 ` Paul Pluzhnikov
2011-05-02 15:00 ` Joseph S. Myers
2011-05-02 15:57 ` Paul Pluzhnikov
2011-05-09 17:01 ` Paul Pluzhnikov
2011-05-09 17:04 ` Paolo Bonzini
2011-05-09 17:26 ` Joseph S. Myers
2011-05-09 17:31 ` Paolo Bonzini
2011-05-09 17:31 ` Joseph S. Myers
2011-05-09 18:00 ` Paul Pluzhnikov
2011-05-10 11:36 ` Richard Guenther
2011-05-10 15:00 ` Ian Lance Taylor [this message]
2011-05-10 15:08 ` Jakub Jelinek
2011-05-10 15:23 ` Paul Pluzhnikov
2011-05-10 15:26 ` Richard Guenther
2011-05-12 9:10 ` Eric Botcazou
2011-05-12 9:19 ` Eric Botcazou
2011-05-12 9:23 ` Paul Pluzhnikov
2011-05-12 9:32 ` Paul Pluzhnikov
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=mcrliyemz5n.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=bonzini@gnu.org \
--cc=dj@redhat.com \
--cc=doko@ubuntu.com \
--cc=gcc-patches@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=neroden@gcc.gnu.org \
--cc=ppluzhnikov@google.com \
--cc=richard.guenther@gmail.com \
--cc=satorux@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).