From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
From: "James A. Robinson" <jim.robinson@gmail.com>
Date: Fri,  4 Nov 2016 23:09:05 +0000
Message-ID: <CAPd04b6w-M9bktCNMZaxY=etBZoQv0NfyKQ2RY7ZfQMgN1AKyw@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: multipart/alternative; boundary=94eb2c07d4285bc0f7054081c3e4
Subject: [9fans] /sys/src/9/port/portfns.h execregs uint vs ulong
Topicbox-Message-UUID: a8e35640-ead9-11e9-9d60-3106f5b1d025

--94eb2c07d4285bc0f7054081c3e4
Content-Type: text/plain; charset=UTF-8

While futzing around with rebuilding a kernel, I noticed that
9atom distributed source tree /sys/src/9/port/portfns.h
declares

void* execregs(uintptr, uint, uint)

but /sys/src/9/pc/trap.c declares

long
execregs(ulong entry, ulong ssize, ulong nargs)

which seems to match all the other architectures
I see under /sys/src/9/.

I can't get to http://plan9.bell-labs.com/sources/
right now, it looks to be offline (I hope me looking
at the wiki and man pages via http earlier wasn't
"too high traffic" for it...), but wondered if this was
an oversight in updating portfns.h.

Jim

--94eb2c07d4285bc0f7054081c3e4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>While futzing around with rebuilding a kernel, I noti=
ced that</div><div>9atom distributed source tree /sys/src/9/port/portfns.h<=
/div><div>declares</div><div><br></div><div>void* execregs(uintptr, uint, u=
int)</div><div><br></div><div>but /sys/src/9/pc/trap.c declares</div><div><=
br></div><div>long</div><div>execregs(ulong entry, ulong ssize, ulong nargs=
)</div><div><br></div><div>which seems to match all the other architectures=
</div><div>I see under /sys/src/9/.</div><div><br></div><div>I can&#39;t ge=
t to=C2=A0<a href=3D"http://plan9.bell-labs.com/sources/">http://plan9.bell=
-labs.com/sources/</a></div><div>right now, it looks to be offline (I hope =
me looking</div><div>at the wiki and man pages via http earlier wasn&#39;t<=
/div><div>&quot;too high traffic&quot; for it...), but wondered if this was=
</div><div>an oversight in updating portfns.h.</div><div><br></div><div>Jim=
</div><div><br></div></div>

--94eb2c07d4285bc0f7054081c3e4--