public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: jbeniston@compxs.com
Cc: 'Dave Korn' <dk@artimi.com>,  binutils@sources.redhat.com
Subject: Re: MEMORY commands in link scripts
Date: Mon, 08 Nov 2004 08:46:00 -0000	[thread overview]
Message-ID: <418F332D.4060007@redhat.com> (raw)
In-Reply-To: <001001c4c33b$12da7510$0bbda8c0@Kindrogan>

Hi Jon,

> I still think it might be useful have ORIGIN() and LENGTH() functions. If I
> were to create a patch to implement this, is it likely to be accepted? 

Yes, provided that a) it worked, b) it was tested and c) you had a 
copyright assignment on file with the FSF.

 >Would overloading the ADDR() and SIZEOF() functions be more approriate?

No, definitely not.  Keep things simple. :-)

Cheers
   Nick


  reply	other threads:[~2004-11-08  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 11:59 Jon Beniston
2004-11-05 12:55 ` Dave Korn
2004-11-05 13:26   ` Jon Beniston
2004-11-08  8:46     ` Nick Clifton [this message]
2004-11-08 11:51       ` Jon Beniston
2004-11-19  9:31         ` Nick Clifton

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=418F332D.4060007@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=dk@artimi.com \
    --cc=jbeniston@compxs.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).