From: Matthew Fortune <Matthew.Fortune@imgtec.com>
To: Alan Modra <amodra@gmail.com>, Hans-Peter Nilsson <hp@bitrange.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: [PATCH] Add new NOCROSSREFSTO linker script command
Date: Fri, 15 Apr 2016 11:12:00 -0000 [thread overview]
Message-ID: <6D39441BF12EF246A7ABCE6654B023537E3D6082@hhmail02.hh.imgtec.org> (raw)
In-Reply-To: <20160414223011.GB27620@bubble.grove.modra.org>
Alan Modra <amodra@gmail.com> writes:
> On Thu, Apr 14, 2016 at 02:08:26PM +0000, Matthew Fortune wrote:
> > This patch introduces a new linker script command NOCROSSREFSTO.
>
> You have my vote for the feature. The patch looks good.
H-P suggested adding an underscore to make the command
NOCROSSREFS_TO:
https://sourceware.org/ml/binutils/2016-04/msg00221.html
I have no objection if this seems clearer. If there are no other
opinions I'll update to add an underscore.
Thanks,
Matthew
next prev parent reply other threads:[~2016-04-15 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 14:08 Matthew Fortune
2016-04-14 22:30 ` Alan Modra
2016-04-15 11:12 ` Matthew Fortune [this message]
2016-04-18 11:15 ` Nick Clifton
2016-04-18 11:49 ` Matthew Fortune
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=6D39441BF12EF246A7ABCE6654B023537E3D6082@hhmail02.hh.imgtec.org \
--to=matthew.fortune@imgtec.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hp@bitrange.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).