public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Matthew Fortune <Matthew.Fortune@imgtec.com>
To: Nick Clifton <nickc@redhat.com>,
	"binutils@sourceware.org"	<binutils@sourceware.org>
Subject: RE: [RFC] Extension to NOCROSSREFS linker script command
Date: Wed, 13 Apr 2016 15:49:00 -0000	[thread overview]
Message-ID: <6D39441BF12EF246A7ABCE6654B023537E3D2F35@hhmail02.hh.imgtec.org> (raw)
In-Reply-To: <570E4DE9.6080502@redhat.com>

Nick Clifton <nickc@redhat.com> writes:
> Hi Matthew,
> 
> > 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?
> 
> Actually this sounds like a sensible approach.
> 
> My concern from a binutils point of view is "is it worth it ?"  Any new
> feature has the possibility of introducing new bugs, and we want to
> avoid feature-creep.  So adding a new feature that is only going to be
> used by one person - ie you - would seem like a bad idea.  Now if there
> were other people also requesting this functionality, then that would be
> a different matter.
> 
> Of course this does not mean you should not create the patch if you want
> to, just that you should be prepared for the possibility that the patch
> might not be accepted into the official sources if we think that it is
> too risky.

Understood and agreed.

I would hope there are other users beyond myself (or rather MIPS embedded
users) who would find this kind of check useful when working with complex
memory layouts in multi-threaded or multi-core environments...

Either way I'll prepare the patch; it is small (sub 30 lines in my first
attempt) but number of lines doesn't always make decisions easier.

Thanks,
Matthew

  reply	other threads:[~2016-04-13 15:49 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 [this message]
2016-04-14 17:27 ` Hans-Peter Nilsson

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=6D39441BF12EF246A7ABCE6654B023537E3D2F35@hhmail02.hh.imgtec.org \
    --to=matthew.fortune@imgtec.com \
    --cc=binutils@sourceware.org \
    --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).