From: Jeffrey Walton <noloader@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: 128-bit data model macros
Date: Sun, 26 Jan 2020 03:07:00 -0000 [thread overview]
Message-ID: <CAH8yC8=GzBCrnz80+8um+7vzqk0YSqKtN02yA3=d9B0wEikjUA@mail.gmail.com> (raw)
In-Reply-To: <20200125124842.GU3191@gate.crashing.org>
On Sat, Jan 25, 2020 at 7:48 AM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> Hi!
>
> On Fri, Jan 24, 2020 at 10:40:47PM -0500, Jeffrey Walton wrote:
> > On 64-bit platforms _LP64 and __LP64__ are defined.
>
> That's not quite true. Those macros mean that "long int" as well as
> pointers are 64 bits, for the selected ABI.
>
> > Do 128-bit machines use the macros _LP128 and __LP128__?
>
> There is __SIZEOF_INT128__, that may be what you are looking for.
Thanks Segher.
Yes, I'm aware of __SIZEOF_INT128__. It is very helpful when available.
I was more interested in ILP128 data model, and its possible use in
the higher end computers. (Does that model even exist?)
Jeff
prev parent reply other threads:[~2020-01-26 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 3:41 Jeffrey Walton
2020-01-25 12:48 ` Segher Boessenkool
2020-01-26 3:07 ` Jeffrey Walton [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='CAH8yC8=GzBCrnz80+8um+7vzqk0YSqKtN02yA3=d9B0wEikjUA@mail.gmail.com' \
--to=noloader@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).