public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [GCC 4.8 changes] PATCH: Mention -maddress-mode=[short|long]
Date: Sun, 17 Feb 2013 19:24:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1302171928550.1859@tuna.site> (raw)
In-Reply-To: <20130211180529.GA5457@intel.com>

On Mon, 11 Feb 2013, H.J. Lu wrote:
> This patch updates GCC 4.8 changes.html to mention
> -maddress-mode=[short|long] for x32.  OK to install?

I made two tweaks on top.  If you can get a colleague who is a
native speaker to have a look, there may be more clarifications/
improvements to make.

Gerald

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.101
diff -u -3 -p -r1.101 changes.html
--- changes.html	17 Feb 2013 12:40:57 -0000	1.101
+++ changes.html	17 Feb 2013 19:05:55 -0000
@@ -465,10 +465,10 @@ B b(42); // OK
     wrong results.  You must build all
     modules with <code>-mpreferred-stack-boundary=3</code>, including any
     libraries.  This includes the system libraries and startup modules.</li>
-    <li>New <code>-maddress-mode=[short|long]</code> option for x32.
+    <li>New <code>-maddress-mode=[short|long]</code> options for x32.
     <code>-maddress-mode=short</code> overrides default 64-bit addresses to
-    32-bit by emitting <code>0x67</code> address-size override prefix. This
-    is the default address mode for x32.</li>
+    32-bit by emitting the <code>0x67</code> address-size override prefix.
+    This is the default address mode for x32.</li>
     <li> New built-in functions to detect run-time CPU type and ISA:
     <ul>
       <li>A built-in function <code>__builtin_cpu_is</code> has been added to

      parent reply	other threads:[~2013-02-17 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 18:05 H.J. Lu
2013-02-12 11:16 ` Richard Biener
2013-02-17 19:24 ` Gerald Pfeifer [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.LNX.2.00.1302171928550.1859@tuna.site \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.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).