public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	gcc-patches@gcc.gnu.org,     Richard Henderson <rth@redhat.com>,
	    "Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: RFC: PATCH: Add -maddress-mode=short|long for x86
Date: Wed, 14 Mar 2012 21:57:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1203142242220.2864@zbenl.fvgr> (raw)
In-Reply-To: <CAFULd4am9BS01JpMcxSnpg7PmoD3O+Ht_0_YVJjOQBJ_BYPq5g@mail.gmail.com>

On Wed, 14 Mar 2012, Uros Bizjak wrote:
> I have also added Gerald to CC, to check if everything is OK with
> added documentation.

Joseph is better with that than I am, but I'll give it a try. :-)

+@item -maddress-mode=long
+@opindex maddress-mode=long
+Generate code for long address mode.  It is only supported for 64-bit
+and x32 environments.  This is the default address mode for 64-bit
+environment.

I cannot formally explain why, but would swap "It" and "This" in
this paragraph and the other.

In any case "64-bit environments" (Plural).

Fine with these changes.


Apart from the above, at least invoke.texi does not define what an x32 
environment is.  Shouldn't that done somewhere (before this terminology
is used)?

Gerald

  parent reply	other threads:[~2012-03-14 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 17:48 H.J. Lu
2012-03-14 19:07 ` Uros Bizjak
2012-03-14 20:13   ` Joseph S. Myers
2012-03-14 21:57   ` Gerald Pfeifer [this message]
2012-03-14 22:34     ` H.J. Lu
2012-03-18 22:17       ` Gerald Pfeifer
2012-03-19 16:02         ` H.J. Lu

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.1203142242220.2864@zbenl.fvgr \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=joseph@codesourcery.com \
    --cc=rth@redhat.com \
    --cc=ubizjak@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).