From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <67325140f16f21e9ac66c77888b22483@brasstown.quanstro.net>
References: <AANLkTikJ3y5exFtTic+8dhUsUqeZBDmR=S-8VzKDK0GH@mail.gmail.com>
	<AANLkTink4CrELJfGf3W15caSYX8Se5ygsm_WeMRdCBz=@mail.gmail.com>
	<AANLkTikUa1KF+8NP54BHicus++YbeZbD48E7z=1H0Y5V@mail.gmail.com>
	<AANLkTinAe_r2EbqOHZGVjaN8yDbhja0m5MUuJfMrn6Cs@mail.gmail.com>
	<AANLkTi=OE2_rZ=ktiw-Rq0c0cHYZVBu9EVtoXhA_UY0z@mail.gmail.com>
	<AANLkTintaOjTpC6Eaz3Ka7256KXYzaDeYg3jsqbCT5Wx@mail.gmail.com>
	<AANLkTim3MH0t6H1522DnHf-P_E7a0rtt6FzY9f3ti10i@mail.gmail.com>
	<AANLkTi=1btTKGVd_gKk+abAjTEwsEPMBhP4L3agrDubg@mail.gmail.com>
	<AANLkTimuhE_G46f0J3nRBos1kVSDvTvUwvUb8u0RsR4A@mail.gmail.com>
	<AANLkTintBhp2pxpdAGnMD2H=1J-gA+cF=GfFzX=MzPrr@mail.gmail.com>
	<67325140f16f21e9ac66c77888b22483@brasstown.quanstro.net>
Date: Sat, 22 Jan 2011 18:56:06 -0800
Message-ID: <AANLkTinpAi4c3PqjVgJwHGxTnoO7qZHJeZ7oShs8B_V1@mail.gmail.com>
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] plan9 go output faults on 9vx with rfork
Topicbox-Message-UUID: a04d8a30-ead6-11e9-9d60-3106f5b1d025

On Sat, Jan 22, 2011 at 6:48 PM, erik quanstrom <quanstro@quanstro.net> wro=
te:

> the plan 9 core needs to religiously use uintptr and not long. =A0long
> is always wrong for these things.

It's a bit messier than that. When 9vx is built as 64-bit, it's a
64-bit kernel supporting 32-bit binaries. uintptr is still a 64-bit
entity. There's no way to take a 32-bit reference parameter as used in
semacquire and treat it as a pointer to a 64-bit item and have it end
well ...

What has to happen is the 9vx syscall interfaces need to be scrubbed
just a bit more for these types of cases and corrected. Or,simpler,
just keep building 32-bit 9vx; that may be the best bet.

ron