From: Gerald Pfeifer <gerald@pfeifer.com>
To: Nick Clifton <nickc@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Sandra Loosemore <sandra@codesourcery.com>,
gcc-patches@gcc.gnu.org
Subject: Re: RFA: Doc update: Describe new MSP430 feature
Date: Tue, 05 May 2015 22:10:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1505060006160.7255@tuna.site> (raw)
In-Reply-To: <87zj5jc9y1.fsf@redhat.com>
Hi Nick,
On Tue, 5 May 2015, Nick Clifton wrote:
> I recently contributes a patch to enhance the MSP430 backend with the
> ability to automatically distribute code and data between high and low
> memory regions. Below is a patch to update the html documentation
> with a description of this new feature. Is it OK to apply ?
as maintainer of the port you do not need anyone else's approval.
That said, I am always happy to provide a second pair of eyes, so
here are some comments:
> Index: htdocs/gcc-5/changes.html
> ===================================================================
> + <li><p>The MSP430 compiler now has the ability to automatically distribute code
> + and data between low (less than 64K) memory and high memory.
Should that be "addresses below ..." or something like that, since
the system would still have more than 64K of memory, not less?
> + This only
> + applies parts
Is a "to" missing here?
> + <p>Two new command line options - <code>-mcode-region=[lower|upper|either]</code>
"command-line options"
Does this really apply to GCC 5, or GCC 6 and the (new) gcc-6/changes.html?
Gerald
next prev parent reply other threads:[~2015-05-05 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 15:37 Nick Clifton
2015-05-05 22:10 ` Gerald Pfeifer [this message]
2015-05-06 9:57 ` Nicholas 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=alpine.LSU.2.20.1505060006160.7255@tuna.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=nickc@redhat.com \
--cc=sandra@codesourcery.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).