From: Ian Lance Taylor <iant@google.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Nick Clifton <nickc@redhat.com>,
Catherine Moore <clm@codesourcery.com>,
binutils@sourceware.org
Subject: Re: PING Re: [RFA] Linker script extension SECTION_FLAGS
Date: Tue, 28 Jun 2011 13:30:00 -0000 [thread overview]
Message-ID: <mcrei2e13tq.fsf@coign.corp.google.com> (raw)
In-Reply-To: <D799BAB5-A295-4F50-A57C-182A325144C4@adacore.com> (Tristan Gingold's message of "Tue, 28 Jun 2011 13:56:31 +0200")
Tristan Gingold <gingold@adacore.com> writes:
> On Jun 28, 2011, at 1:37 PM, Nick Clifton wrote:
>
>> Hi Catherine,
>>
>>> Thanks for the patch review. I've developed a new patch that addresses
>>> the comments that both you and Tristan made regarding the original
>>> patch. I've now associated the INPUT_SECTION_FLAGS with the input
>>> section specifications instead of the output sectionas you and others
>>> suggested. I've tested arm-coff, mips-elf and ppc-elf. What do you
>>> think? Is this okay to commit?
>
> [...]
>
>> * You have not provided a patch for GOLD. I would like to keep the two linkers in sync, at least as far as features go.
>
> Should we really require that ? I think that this is asking too much. There are some interesting features in gold (such as ICF)
> that aren't in ld; so they are already not in sync.
Yeah, I agree. I would very much like gold to be in sync, but I don't
think we can reasonably request it of patch writers. Gold does not yet
support all the linker script features of GNU ld; e.g.,
DATA_SEGMENT_RELRO_END is not correctly supported (gold implements relro
directly rather than via linker script shenanigans).
Ian
next prev parent reply other threads:[~2011-06-28 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 19:32 Catherine Moore
2011-05-18 19:33 ` Catherine Moore
2011-05-19 0:07 ` Ian Lance Taylor
2011-05-24 22:57 ` Catherine Moore
2011-05-25 12:28 ` Tristan Gingold
2011-06-06 22:02 ` PING " Catherine Moore
2011-06-07 13:11 ` Nick Clifton
2011-06-22 21:32 ` Catherine Moore
2011-06-28 11:37 ` Nick Clifton
2011-06-28 11:56 ` Tristan Gingold
2011-06-28 12:22 ` Nick Clifton
2011-06-28 13:30 ` Ian Lance Taylor [this message]
2011-06-30 21:11 ` Catherine Moore
2011-07-11 13:55 ` Nick Clifton
2012-02-09 5:27 ` Alan Modra
2011-05-19 7:44 ` Tristan Gingold
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=mcrei2e13tq.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=clm@codesourcery.com \
--cc=gingold@adacore.com \
--cc=nickc@redhat.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).