From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 64-Bit programming model.
Date: Fri, 30 Sep 2005 09:14:26 -0700 [thread overview]
Message-ID: <9ab217670509300914h1f61ababh@mail.gmail.com> (raw)
In-Reply-To: <3d9930aa542f29f26c3014fa5cf12f7a@terzarima.net>
2005/9/30, Charles Forsyth <forsyth@terzarima.net>:
> on amd64 it is:
>
> short is 16 bits, as before for Plan 9
> int and long are 32 bits, as before
> long long is 64 bits, also as before
> pointers are 64 bits, not as before. (it's that last bit causes most of the trouble.)
Yeah, way too much code in Unix that uses void pointer to integer
casting. ``Oops''.
> i think it must be LLP64 in your scheme
At least in Solaris the #define for both amd64 and SPARC64 is `LP64'.
This is found in one of the include files under feature_tests.h (see
cvs.opensolaris.org).
--Devon
>
>
> ---------- Doorgestuurd bericht ----------
> From: Vester Thacker <vester.thacker@gmail.com>
> To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
> Date: Fri, 30 Sep 2005 04:31:45 -0700
> Subject: [9fans] 64-Bit programming model.
> Okay, time for the "dumb question of the month".
>
> Concerning Plan 9 64-Bit support, which Long Pointer programming model
> is being used with Sparc64 and AMD64 ports? LLP64, LP64 or ILP64. Just
> curious.
>
> Forgive my ignorance, I am a layman and nowadays get my schooling
> though search engine results.
>
> --vester
>
>
next prev parent reply other threads:[~2005-09-30 16:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 11:31 Vester Thacker
2005-09-30 13:31 ` Charles Forsyth
2005-09-30 15:18 ` David Leimbach
2005-09-30 15:44 ` Karl Magdsick
2005-09-30 16:06 ` Charles Forsyth
[not found] ` <45544405a9a74e554cd5b645a672fb3e@terzarima.net>
2005-09-30 16:14 ` Karl Magdsick
2005-09-30 16:21 ` Russ Cox
2005-09-30 16:53 ` bakul+plan9
2005-09-30 16:14 ` Devon H. O'Dell [this message]
2005-09-30 18:07 ` Charles Forsyth
2005-09-30 19:01 ` erik quanstrom
2005-10-01 13:52 ` Charles Forsyth
2005-10-01 23:37 ` Ronald G Minnich
[not found] ` <f344c691fd8960b43b2c77f308ed2ea3@terzarima.net>
2005-09-30 21:27 ` Vester Thacker
2005-09-30 23:28 ` Jim McKie
2005-10-01 3:09 ` Ronald G Minnich
2005-10-01 3:19 ` Devon H. O'Dell
2005-10-01 4:46 ` erik quanstrom
2005-10-01 22:50 ` Jim McKie
2005-10-01 23:43 ` erik quanstrom
2005-10-01 13:50 ` Russ Cox
2005-10-01 18:28 ` Devon H. O'Dell
2005-10-01 14:28 ` Charles Forsyth
2005-10-01 14:20 ` Charles Forsyth
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=9ab217670509300914h1f61ababh@mail.gmail.com \
--to=devon.odell@gmail.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).