From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 16bit C compilers
Date: Fri, 15 Feb 2002 09:55:48 +0000 [thread overview]
Message-ID: <3C6C8C30.42428AE7@null.net> (raw)
In-Reply-To: <1463098921@snellwilcox.com>
steve.simon@snellwilcox.com wrote:
> anyone tried to port it to a 16 bit CPU?
What is a "16-bit CPU"?
If you mean that a single address space is limited to 2^16 bytes,
then that seems to be too small for Plan9.
If you mean that the fast registers are 16 bits wide,
then the porting job shouldn't be any worse than for 32-bit wide
registers, all other architectural details being equal. (But it
will run slower.) Or at least I *hope* the Plan9 coders used
long instead of int when they needed more than 16 bits, something
that has been standard practice since about 1977.
next prev parent reply other threads:[~2002-02-15 9:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 16:15 steve.simon
2002-02-15 9:55 ` Douglas A. Gwyn [this message]
2002-02-15 9:28 nigel
2002-02-15 9:41 Fco.J.Ballesteros
2002-02-15 12:14 forsyth
2002-02-15 12:21 ` Boyd Roberts
2002-02-15 12:30 forsyth
2002-02-15 13:57 Russ Cox
2002-02-15 14:02 ` Boyd Roberts
2002-02-18 10:14 ` Douglas A. Gwyn
2002-02-18 11:37 ` Boyd Roberts
2002-02-15 13:59 Russ Cox
2002-02-15 14:08 Fco.J.Ballesteros
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
[not found] <miller@hamnavoe.demon.co.uk>
2002-02-18 17:43 ` Richard Miller
2002-02-18 18:14 ` Scott Schwartz
2002-02-20 10:55 forsyth
2002-02-22 16:15 anothy
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=3C6C8C30.42428AE7@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).