From: John Love-Jensen <eljay@adobe.com>
To: corey taylor <corey.taylor@gmail.com>, <gcc-help@gnu.org>
Subject: Re: long long in 64-bit modes
Date: Fri, 14 Oct 2005 12:22:00 -0000 [thread overview]
Message-ID: <BF750C7E.311D%eljay@adobe.com> (raw)
In-Reply-To: <2e393d080510092219w71bdf812y4083ab429d14278e@mail.gmail.com>
Hi Corey,
(Sorry for the delay, I was out of town.)
> How does the long long type change in 64-bit modes for C and C++?
>
> Does it stay 64-bit and is deprecated for long?
My expectation is:
int - natural word size of the architecture
short - half the word size of the architecture
long - twice the word size of the architecture
long long - (if available at all) twice the size of long
NOTE: my expectation differs from the C/C++ standard as the constraints of
those data types.
So for a 64-bit architecture:
short - 32 bit
int - 64 bit
long - 128 bit
long long - 256 bit
That's my expectation. That's not what I'm seeing on the 64-bit platforms I
work on.
However, for me, an acceptable alternative is C99's <stdint.h>.
--Eljay
prev parent reply other threads:[~2005-10-14 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 5:20 corey taylor
2005-10-14 12:22 ` John Love-Jensen [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=BF750C7E.311D%eljay@adobe.com \
--to=eljay@adobe.com \
--cc=corey.taylor@gmail.com \
--cc=gcc-help@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).