From: Hans-Peter Nilsson <hp@bitrange.com>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [RFC] Extension to NOCROSSREFS linker script command
Date: Thu, 14 Apr 2016 17:27:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.02.1604141323490.25085@arjuna.pair.com> (raw)
In-Reply-To: <6D39441BF12EF246A7ABCE6654B023537E3D0B33@hhmail02.hh.imgtec.org>
On Tue, 12 Apr 2016, Matthew Fortune wrote:
> My proposal is relatively simple... A new command to check one direction
> only:
>
> NOCROSSREFSTO (<to-section> , <from-section1> , <from-section2> ...)
>
> The implementation of this in LD is pretty trivial. Any thoughts on this
> or alternative approaches?
Today's bikeshed: IMHO there are now one too many juxtaposed
words there. NOCROSSREFS_TO?
brgds, H-P
prev parent reply other threads:[~2016-04-14 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 13:51 Matthew Fortune
2016-04-13 13:47 ` Nick Clifton
2016-04-13 15:49 ` Matthew Fortune
2016-04-14 17:27 ` Hans-Peter Nilsson [this message]
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.BSF.2.02.1604141323490.25085@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=binutils@sourceware.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).