From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] ken-cc, 64 bits machine, and 32 bits integers
Date: Tue, 30 Mar 2010 15:52:27 -0400 [thread overview]
Message-ID: <b938a449d57f533665ca616cb7a998a8@coraid.com> (raw)
In-Reply-To: <20100330193718.GA3120@polynum.com>
> 1) If a compiler set on a 32 bits machine, "long" to be 64 bits? (I
> haven't looked at the sources, but I guess it is not the case for ken-cc
> suite).
>
> 2) On a 64 bits (since Charles Forsyth has done work for amd64 at least
> on ken-cc, this exists), I imagine "long" is an octa (64 bits).
with kenc, long === 32 bits even on 64 bit machines; there is no
difference in storage size between long and int.
- erik
next prev parent reply other threads:[~2010-03-30 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 19:37 tlaronde
2010-03-30 19:52 ` erik quanstrom [this message]
2010-03-30 19:56 ` EBo
2010-03-30 20:03 ` Devon H. O'Dell
2010-03-30 20:11 ` Charles Forsyth
2010-03-30 22:29 ` tlaronde
2010-03-30 20:54 ` Patrick Kelly
2010-03-30 22:34 ` tlaronde
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=b938a449d57f533665ca616cb7a998a8@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).