From: Martin Sebor <msebor@gmail.com>
To: David Brown <david@westcontrol.com>,
Kostas Savvidis <ksavvidis@gmail.com>,
gcc-help@gcc.gnu.org
Subject: Re: 128-bit integer - nonsensical documentation?
Date: Thu, 27 Aug 2015 15:09:00 -0000 [thread overview]
Message-ID: <55DF2814.3050206@gmail.com> (raw)
In-Reply-To: <55DEB83C.5010106@westcontrol.com>
> Is it fair to say that the main use of extended integers is to "fill the
> gaps" if the sequence char, short, int, long, long long has missing
> sizes? Such as if an architecture defines int to be 64-bit and short to
> be 32-bit, then you could have an extended integer type for 16-bit?
Something like that. The extended integer types were invented by
the committee in hopes of a) easing the transition from 16-bit
to 32-bit to 64-bit implementations and b) making it possible for
implementers targeting new special-purpose hardware to extend the
language in useful and hopefully consistent ways to take advantage
of the new hardware. One idea was to support bi-endian types in
the type system. There was no experience with these types when
they were introduced and I don't have the impression they've been
as widely adopted as had been envisioned. Intel Bi-endian compiler
does provide support for "extended" mixed-endian types in the same
program.
Martin
next prev parent reply other threads:[~2015-08-27 15:09 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 [this message]
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=55DF2814.3050206@gmail.com \
--to=msebor@gmail.com \
--cc=david@westcontrol.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).