From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] ulong
Date: Wed, 18 Jan 2006 03:55:26 +1100 [thread overview]
Message-ID: <775b8d190601170855u10fe7d95gc268a7da50fbf1de@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0601170430h77cf43c6p1735906a15ceb3f4@mail.gmail.com>
i've seen code that uses 53 where i suspect it means 54.
rarely does any "fancy casting stuff" work on more than
one platform.
brucee
On 1/17/06, Russ Cox <rsc@swtch.com> wrote:
> > > (vlong)(...|((p)[3]<<24)) sign extends. Casting the (p)[0]
> > > to (ulong) has the effect of making the whole 32-bit expression
> > > unsigned on 32-bit systems, but if ulong is 64 bits, then
> > > you'll still sign-extend ((p)[3]<<24) during the convertsion
> > > from int to ulong.
> >
> > i'd be careful to define ulong to be 32 bits for all plan 9 source
> > including p9p (using `ulong == unsigned int' if necessary).
> > otherwise quite a bit more will break.
> > having fcall.h use u32int is fine too, of course, just to make the point clearer
>
> I started out doing ulong==unsigned int (cf. drawterm),
> but that implies long==int, and I just couldn't bear to do
> that for p9p. I've been fixing problems as they come up.
> Libmemdraw needed changes (which I expected), and
> libmp did too (which I didn't). Do you know of other code?
>
> Russ
>
prev parent reply other threads:[~2006-01-17 16:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 11:35 [9fans] Brdline Gorka guardiola
2006-01-16 12:30 ` Charles Forsyth
2006-01-16 13:27 ` Bruce Ellis
2006-01-16 13:37 ` Gorka guardiola
2006-01-16 13:57 ` Charles Forsyth
2006-01-16 14:24 ` Bruce Ellis
2006-01-17 0:56 ` erik quanstrom
2006-01-17 1:35 ` Russ Cox
2006-01-17 1:42 ` erik quanstrom
2006-01-17 1:47 ` Russ Cox
2006-01-17 10:01 ` Charles Forsyth
2006-01-17 16:45 ` Bruce Ellis
2006-01-18 5:38 ` Simon Williams
2006-01-18 5:49 ` Bruce Ellis
2006-01-18 5:54 ` Paul Lalonde
2006-01-18 6:11 ` Bruce Ellis
2006-01-18 14:25 ` Bruce Ellis
2006-01-18 15:26 ` Ronald G Minnich
2006-01-18 23:06 ` Adrian Tritschler
2006-01-19 1:20 ` Bruce Ellis
2006-01-18 15:45 ` Paul Lalonde
2006-01-18 16:41 ` Bruce Ellis
2006-01-18 16:47 ` Wes Kussmaul
2006-01-18 16:57 ` Bruce Ellis
2006-01-18 17:37 ` David Leimbach
2006-01-18 17:50 ` Bruce Ellis
2006-01-18 18:00 ` Sape Mullender
2006-01-18 17:01 ` Paul Lalonde
2006-01-18 17:30 ` Charles Forsyth
2006-01-18 18:04 ` Wes Kussmaul
2006-01-18 20:22 ` Skip Tavakkolian
2006-01-18 20:31 ` andrey mirtchovski
2006-01-18 23:01 ` Bruce Ellis
2006-01-18 22:56 ` Joel Salomon
2006-01-18 15:25 ` Brantley Coile
2006-01-18 16:35 ` Paul Lalonde
2006-01-17 9:59 ` [9fans] ulong Charles Forsyth
2006-01-17 12:30 ` Russ Cox
2006-01-17 16:55 ` Bruce Ellis [this message]
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=775b8d190601170855u10fe7d95gc268a7da50fbf1de@mail.gmail.com \
--to=bruce.ellis@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).