From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 16bit C compilers
Date: Mon, 18 Feb 2002 10:14:27 +0000 [thread overview]
Message-ID: <3C6E021B.3F8856E0@null.net> (raw)
In-Reply-To: <3C6D14D9.6D0C9451@strakt.com>
Boyd Roberts wrote:
> int was always intended to be the machine's 'word' size [64 bit].
ISAs aren't always so simple these days; orginally a "word"
was a common measure for instruction, non-floating datum,
address, width of data bus, with of memory access, etc., but
now these often don't match each other so one is hard-put to
name a definite "word" size.
A C implementor might well choose "int" to be 32 bits even
on a machine where 64 bits would be more natural, in order
to ease importing of code written sloppily on a so-called
32-bit platform.
next prev parent reply other threads:[~2002-02-18 10:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 13:57 Russ Cox
2002-02-15 14:02 ` Boyd Roberts
2002-02-18 10:14 ` Douglas A. Gwyn [this message]
2002-02-18 11:37 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 16:15 anothy
2002-02-20 10:55 forsyth
[not found] <miller@hamnavoe.demon.co.uk>
2002-02-18 17:43 ` Richard Miller
2002-02-18 18:14 ` Scott Schwartz
2002-02-18 13:14 forsyth
2002-02-20 10:08 ` Thomas Bushnell, BSG
2002-02-20 17:59 ` Scott Schwartz
2002-02-21 9:40 ` Douglas A. Gwyn
2002-02-21 10:08 ` Boyd Roberts
2002-02-21 18:06 ` Thomas Bushnell, BSG
2002-02-21 22:46 ` George Michaelson
2002-02-22 9:58 ` Thomas Bushnell, BSG
2002-02-22 10:58 ` George Michaelson
2002-02-15 14:08 Fco.J.Ballesteros
2002-02-15 13:59 Russ Cox
2002-02-15 12:30 forsyth
2002-02-15 12:14 forsyth
2002-02-15 12:21 ` Boyd Roberts
2002-02-15 9:41 Fco.J.Ballesteros
2002-02-15 9:28 nigel
2002-02-14 16:15 steve.simon
2002-02-15 9:55 ` Douglas A. Gwyn
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=3C6E021B.3F8856E0@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/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).