From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [patch] Improve docs for 128-bit integers in extend.texi
Date: Tue, 22 Jan 2013 21:58:00 -0000 [thread overview]
Message-ID: <CAH6eHdQOqmVuuGv4+G7KQETfphzOtxNpFEJLLa+EhnLsU1nbDQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 77 bytes --]
Committed as obvious.
* doc/extend.texi (__int128): Improve grammar.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1233 bytes --]
commit b907a92691dbabe5755bc82c5e66718c8b255f4c
Author: Jonathan Wakely <jwakely.gcc@gmail.com>
Date: Tue Jan 22 21:36:04 2013 +0000
* doc/extend.texi (__int128): Improve grammar.
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 8ce6e1e..076aa68 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -811,15 +811,15 @@ the middle operand uses the value already computed without the undesirable
effects of recomputing it.
@node __int128
-@section 128-bits integers
+@section 128-bit integers
@cindex @code{__int128} data types
As an extension the integer scalar type @code{__int128} is supported for
-targets having an integer mode wide enough to hold 128 bits.
+targets which have an integer mode wide enough to hold 128 bits.
Simply write @code{__int128} for a signed 128-bit integer, or
@code{unsigned __int128} for an unsigned 128-bit integer. There is no
-support in GCC to express an integer constant of type @code{__int128}
-for targets having @code{long long} integer less than 128 bits wide.
+support in GCC for expressing an integer constant of type @code{__int128}
+for targets with @code{long long} integer less than 128 bits wide.
@node Long Long
@section Double-Word Integers
reply other threads:[~2013-01-22 21:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAH6eHdQOqmVuuGv4+G7KQETfphzOtxNpFEJLLa+EhnLsU1nbDQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).