From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat, 22 Jan 2011 22:00:31 -0500
To: 9fans@9fans.net
Message-ID: <8a9a463a44262b0750c031aa23208398@brasstown.quanstro.net>
In-Reply-To: <AANLkTinpAi4c3PqjVgJwHGxTnoO7qZHJeZ7oShs8B_V1@mail.gmail.com>
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=1>
	<AANLkTinpAi4c3PqjVgJwHGxTnoO7qZHJeZ7oShs8B_V1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] plan9 go output faults on 9vx with rfork
Topicbox-Message-UUID: a054eee2-ead6-11e9-9d60-3106f5b1d025

> 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 ...

right.  i think the situation confused me.  but i don't feel too bad.
the linux guys, with their 10s of thousands can't get this right.

> 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.

that makes more sense to me.

- erik