From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Kostas Savvidis <ksavvidis@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: 128-bit integer - nonsensical documentation?
Date: Wed, 26 Aug 2015 12:39:00 -0000 [thread overview]
Message-ID: <CAH6eHdSvEGAVMnpH9US8Q9yY-s0xRyFmyko1p2SZsTLSH4ek-A@mail.gmail.com> (raw)
In-Reply-To: <93EE7806-1082-4A59-B5FB-6758E0532049@gmail.com>
On 26 August 2015 at 13:32, Kostas Savvidis wrote:
> I sense there is a consensus that
> 1) the 128bit integer is emulated emulated on 64-bit platforms, not available on 32-bit platforms, and is not native anywhere
> 2) the long long int is 64-bits everywhere so you can *NEVER* do what the document seems to suggest one *MIGHT* be able to do — input a 128-bit constant
>
> To me, this would justify rewriting the documentation.
I disagree, it is correct as written. There may be ports outside the
GCC tree where you can write a 128-bit constant (there may even be
some in the tree, I don't know).
> My personal lament is that i still cannot find out anywhere if it is available on all 64-bit platforms or on intel only.
It's not Intel only, it works fine on powerpc64le, for example.
next prev parent reply other threads:[~2015-08-26 12:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 11:04 Kostas Savvidis
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 [this message]
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=CAH6eHdSvEGAVMnpH9US8Q9yY-s0xRyFmyko1p2SZsTLSH4ek-A@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=ksavvidis@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).