From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: 128-bit long long?
Date: Sun, 21 Mar 2004 21:20:00 -0000 [thread overview]
Message-ID: <405DEB4F.4020604@coyotegulch.com> (raw)
In-Reply-To: <8765cykqws.fsf@egil.codesourcery.com>
Zack Weinberg wrote:
> Best current practice appears to be to provide an "extended integral
> type" __int128. This doesn't have the problems of 'long long' because
> it's not a *basic* integral type (in particular, it cannot be used for
> size_t).
I always wondered why C99 didn't define both int128_t and uint128_t in
<stdint.h>.
..Scott
next prev parent reply other threads:[~2004-03-21 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 17:34 Scott Robert Ladd
2004-03-21 17:37 ` Andreas Jaeger
2004-03-21 18:02 ` Paolo Carlini
2004-03-21 20:27 ` Erik Trulsson
2004-03-21 20:52 ` Zack Weinberg
2004-03-21 21:11 ` Joseph S. Myers
2004-03-21 21:20 ` Scott Robert Ladd [this message]
2004-03-22 0:12 ` Paolo Carlini
2004-03-24 5:38 ` Richard B. Kreckel
2004-03-24 5:57 ` Paolo Carlini
2004-03-30 2:10 ` Jim Wilson
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=405DEB4F.4020604@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.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).