From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ports ...
Date: Tue, 24 Jun 2003 06:53:03 -0700 [thread overview]
Message-ID: <20030624135303.GX7193@cassie.foobarbaz.net> (raw)
In-Reply-To: <f7f9898c7ff3e263b6dd7e2fa310d894@plan9.bell-labs.com>
On Thu, Jun 05, 2003 at 09:18:21AM -0400, David Presotto wrote:
> It would be work to move to 64 bit pointers. Not infinite
> though. The reliance is more on ulong and pointer being
> the same size. If they're both 64 bits, it'll be pretty
> easy. The truly hard part is changing the compiler and
> debugging it afterwards. If you have to simultaneously
> rewrite a compiler and do a port, its much easier to have
> multiple people.
Taking a break from coding something else, I did a tiny
bit of research.
All of amd64, alpha, and sparc64 have ulong and pointer
being 64-bit on all the platforms I surveyed. That would
make the part about reliance on ulong and pointer being
64-bit a non-issue.
Of course, there are the other hurdles... :)
--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin
next prev parent reply other threads:[~2003-06-24 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 4:31 ron minnich
2003-06-05 4:59 ` Christopher Nielsen
2003-06-05 13:18 ` David Presotto
2003-06-24 13:53 ` Christopher Nielsen [this message]
2003-06-24 14:17 ` boyd, rounin
2003-06-24 17:15 ` Douglas A. Gwyn
2003-06-24 20:33 ` boyd, rounin
2003-06-24 20:38 ` Joel Salomon
2003-06-05 14:11 ` jmk
2003-06-05 15:29 ` Jack Johnson
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=20030624135303.GX7193@cassie.foobarbaz.net \
--to=cnielsen@pobox.com \
--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).