From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no
	version=3.4.4
Received: (qmail 32160 invoked from network); 16 Mar 2022 19:41:22 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 16 Mar 2022 19:41:22 -0000
Received: from balrog.mythic-beasts.com ([46.235.227.24]) by 4ess; Wed Mar 16 15:29:51 -0400 2022
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=quintile.net; s=mythic-beasts-k1; h=To:Date:Subject:From;
	bh=bPLD4nX48Lnxq+4D2xti806LUZH1XcYXDIDNiiNd73U=; b=Y39YLcjeC2WqQbAgAkQiCyug27
	NQYCpyhH/9wM+5ppvNHvgMI6eeDzkJOQvK6tJYK6Gx1p0KEI34L7VrlRPIAk02hplvpTFcuEFcyeR
	aPSXPXrfvxVBLA5/sN2wz7nrNbNMUZMNs6kigo+ull6bKbo9rrN0AGDTz3Tfiv4abnondNReHun1u
	x3pw+a4OHWnuQhSUYG1wrEntA2UXVTqwAZXhMiGsar/Itr9JwE272s8Mr/umhsaW4OMUEV1GsMb4Z
	+HBmzJeQWUcFGfDGp+cOssPW3yBBxTUexa3T+/aQES187v3GT5Lh1UjZLzq+PgysrSGEtDlUL8hyF
	C0pC5z/Q==;
Received: from [81.187.198.132] (port=50722 helo=smtpclient.apple)
	by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92.3)
	(envelope-from <steve@quintile.net>)
	id 1nUZL7-0008Va-E5
	for 9front@9front.org; Wed, 16 Mar 2022 19:29:49 +0000
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Steve Simon <steve@quintile.net>
Mime-Version: 1.0 (1.0)
Date: Wed, 16 Mar 2022 19:29:43 +0000
Message-Id: <AE177648-F2A4-41E2-9CA1-E772F134EDC8@quintile.net>
References: <983983D5-BCC6-4187-9F01-70C81C81ABE0@firstpost.pub>
In-Reply-To: <983983D5-BCC6-4187-9F01-70C81C81ABE0@firstpost.pub>
To: 9front@9front.org
X-Mailer: iPhone Mail (19D52)
X-BlackCat-Spam-Score: 4
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: decentralized just-in-time session core layer 
Subject: Re: [9front] Go: "exec header invalid"
Reply-To: 9front@9front.org
Precedence: bulk


i would ask in gonuts google group, and ask richard miller who did the plan9=
 arm32 port i believe - they are likely to be able tobhelp.

-Steve




> On 16 Mar 2022, at 5:07 pm, sml <sml@firstpost.pub> wrote:
>=20
> =EF=BB=BF
>>=20
>> Am 15.03.2022 um 12:15 schrieb Philip Silva <philip.silva@protonmail.com>=
:
>>=20
>> Actually there's also a 500$ bounty for this
>>=20
>> http://fqa.9front.org/appendixb.html
>=20
> I would like to add 50$ for this.
>=20
>=20
> At the moment, I=E2=80=99m trying to understand how plan9/arm is implement=
ed, to get an idea what needs to be done for plan9/arm64.=20
>=20
> As far as I understand,  /src/syscall/mksysnum_plan9.sh in go is used to g=
et the information from /src/libc/9syscall/sys.h from plan9, using it in /sr=
c/syscall/zsysnum_plan9.go and at the beginning of /src/runtime/sys_plan9_ar=
m.s.
>=20
> /src/runtime/defs_plan9_arm.go is the information from /arm/include/ureg.h=
 with getter and setter functions.
>=20
> But there are files like:
>    /src/runtime/os_plan9_arm.go
>    /src/runtime/rt0_plan9_arm.s
>    /src/runtime/sys_plan9_arm.s (the part below the sysnums)
>    /src/syscall/asm_plan9_arm.s
>    /src/syscall/syscall_plan9.go
>    /src/syscall/zsyscall_plan9_arm.go
> for which I cannot find the source in the plan9 code.
>=20
> Is there documentation about the go code itself, regarding the machine dep=
endent parts?
>=20
> And do you know where I can find the plan9 counterparts to some of the fil=
es listed above?
>=20
> Thank you very much in advance!
>=20
> Best regards,=20
> sml
>=20