From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] plan9 go output faults on 9vx with rfork
Date: Sat, 22 Jan 2011 22:00:31 -0500 [thread overview]
Message-ID: <8a9a463a44262b0750c031aa23208398@brasstown.quanstro.net> (raw)
In-Reply-To: <AANLkTinpAi4c3PqjVgJwHGxTnoO7qZHJeZ7oShs8B_V1@mail.gmail.com>
> 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
next prev parent reply other threads:[~2011-01-23 3:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikJ3y5exFtTic+8dhUsUqeZBDmR=S-8VzKDK0GH@mail.gmail.com>
[not found] ` <AANLkTink4CrELJfGf3W15caSYX8Se5ygsm_WeMRdCBz=@mail.gmail.com>
[not found] ` <AANLkTikUa1KF+8NP54BHicus++YbeZbD48E7z=1H0Y5V@mail.gmail.com>
[not found] ` <AANLkTinAe_r2EbqOHZGVjaN8yDbhja0m5MUuJfMrn6Cs@mail.gmail.com>
2011-01-20 6:59 ` ron minnich
2011-01-20 16:48 ` David Leimbach
[not found] ` <AANLkTintaOjTpC6Eaz3Ka7256KXYzaDeYg3jsqbCT5Wx@mail.gmail.com>
[not found] ` <AANLkTim3MH0t6H1522DnHf-P_E7a0rtt6FzY9f3ti10i@mail.gmail.com>
[not found] ` <AANLkTi=1btTKGVd_gKk+abAjTEwsEPMBhP4L3agrDubg@mail.gmail.com>
[not found] ` <AANLkTimuhE_G46f0J3nRBos1kVSDvTvUwvUb8u0RsR4A@mail.gmail.com>
[not found] ` <AANLkTiki2v5MgdxwgjQpJopnrRQhBXKm80+aua_FFAef@mail.gmail.com>
[not found] ` <AANLkTi=fi2Xm0R1Jx2NcrKUkyJaYqnizDP0xJPgaenMY@mail.gmail.com>
2011-01-23 2:43 ` ron minnich
2011-01-23 2:48 ` erik quanstrom
2011-01-23 2:56 ` ron minnich
2011-01-23 3:00 ` erik quanstrom [this message]
2011-01-23 19:20 ` Charles Forsyth
2011-01-23 19:15 ` Devon H. O'Dell
2011-01-23 20:40 ` EBo
2011-01-23 22:00 ` ron minnich
2011-01-24 12:11 ` EBo
2011-01-24 17:18 ` yy
2011-01-24 17:24 ` erik quanstrom
2011-01-25 14:28 ` Richard Miller
2011-01-24 17:24 ` ron minnich
2011-02-08 0:05 ` yy
2011-01-24 20:02 ` Steve Simon
2011-01-23 23:40 ` Charles Forsyth
2011-01-24 1:18 ` ron minnich
2011-01-24 12:17 ` EBo
2011-01-24 17:16 ` ron minnich
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=8a9a463a44262b0750c031aa23208398@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).