From: Tristan Gingold <gingold@adacore.com>
To: Richard Sandiford <richard.sandiford@linaro.org>
Cc: Catherine Moore <clm@codesourcery.com>, binutils@sourceware.org
Subject: Re: Comments requested for proposed for ld scripting language extension
Date: Tue, 03 May 2011 08:52:00 -0000 [thread overview]
Message-ID: <0AADE1A0-9840-46A7-98E0-2DC973A4E1FA@adacore.com> (raw)
In-Reply-To: <g4oc3kxjfz.fsf@linaro.org>
On May 3, 2011, at 10:44 AM, Richard Sandiford wrote:
> Tristan Gingold <gingold@adacore.com> writes:
>> I also think that you could make the design a little bit generic and
>> allow boolean negation. What about something like:
>
> Sounds good, but...
>
>>
>> .text : FLAGS (-SHF_PPC_VLE)
>> {
>> *(.text .text.* .gnu.linkonce.t.*)
>> } >ram
>> .text_vle : FLAGS (+SHF_PPC_VLE)
>> {
>> *(.text .text.* .gnu.linkonce.t.*)
>> } >ram
>
> ...how about using C operators (SHF_PPC_VLE and !SHF_PPC_VLE) instead?
> That'd be more consistent with other script expressions.
Sure.
>> Finally I wonder if the flags shouldn't be in the input section part,
>> in order to make this feature even more generic:
>>
>> .text :
>> {
>> *(.text .text.* .gnu.linkonce.t.*) FLAGS (-SHF_PPC_VLE)
>> } >ram
>
> While this might be useful in some cases, I think Catherine's version
> is going to make the usual case easier. FWIW, I agree with Alan that
> it fits nicely with the existing ONLY_IF_* constraints.
>
> Richard
next prev parent reply other threads:[~2011-05-03 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 16:48 Catherine Moore
2011-04-29 0:24 ` Alan Modra
2011-04-29 7:35 ` Tristan Gingold
2011-05-03 8:44 ` Richard Sandiford
2011-05-03 8:52 ` Tristan Gingold [this message]
2011-05-03 14:35 ` Catherine Moore
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=0AADE1A0-9840-46A7-98E0-2DC973A4E1FA@adacore.com \
--to=gingold@adacore.com \
--cc=binutils@sourceware.org \
--cc=clm@codesourcery.com \
--cc=richard.sandiford@linaro.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).