From: Kostas Savvidis <ksavvidis@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: 128-bit integer - nonsensical documentation?
Date: Wed, 26 Aug 2015 11:04:00 -0000 [thread overview]
Message-ID: <1B1111BE-E274-4C80-8189-22B78D77647A@gmail.com> (raw)
The online documentation contains the attached passage as part of the "C-Extensions” chapter. There are no actual machines which have an " integer mode wide enough to hold 128 bits” as the document puts it. This would be a harmless confusion if it didn’t go on to say “… long long integer less than 128 bits wide” (???!!!) Whereas in reality "long long int” is 64 bits everywhere i have seen.
KS
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6.8 128-bit integers
As an extension the integer scalar type __int128 is supported for targets which have an integer mode wide enough to hold 128 bits. Simply write __int128 for a signed 128-bit integer, or unsigned __int128 for an unsigned 128-bit integer. There is no support in GCC for expressing an integer constant of type __int128 for targets with long long integer less than 128 bits wide.
next reply other threads:[~2015-08-26 11:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 11:04 Kostas Savvidis [this message]
2015-08-26 11:44 ` Jeffrey Walton
2015-08-26 12:13 ` David Brown
2015-08-26 16:02 ` Martin Sebor
2015-08-27 7:12 ` David Brown
2015-08-27 9:32 ` Jonathan Wakely
2015-08-27 9:42 ` Marc Glisse
2015-08-27 9:43 ` Jonathan Wakely
2015-08-27 15:09 ` Martin Sebor
2015-08-28 6:54 ` David Brown
2015-08-28 15:30 ` Martin Sebor
2015-08-26 12:22 ` Jonathan Wakely
2015-08-26 12:32 ` Kostas Savvidis
2015-08-26 12:39 ` Jonathan Wakely
2015-08-26 12:47 ` Jeffrey Walton
2015-08-26 12:47 ` David Brown
2015-08-26 12:48 ` Jeffrey Walton
2015-08-26 12:51 ` Marc Glisse
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=1B1111BE-E274-4C80-8189-22B78D77647A@gmail.com \
--to=ksavvidis@gmail.com \
--cc=gcc-help@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).