From: sml <sml@firstpost.pub>
To: 9front@9front.org
Subject: Re: [9front] Go: "exec header invalid"
Date: Wed, 16 Mar 2022 08:43:23 +0100 [thread overview]
Message-ID: <983983D5-BCC6-4187-9F01-70C81C81ABE0@firstpost.pub> (raw)
In-Reply-To: <OomzI3kIVXAxCxF4zuydqqnxcDkSe9FTV5lp-zMcUAm1n7L7GAgj4DO5sm9REG39PpKCQOJ1qypK93M47phY319AM6JFh_CCZ92BPzhJbLY=@protonmail.com>
> Am 15.03.2022 um 12:15 schrieb Philip Silva <philip.silva@protonmail.com>:
>
> Actually there's also a 500$ bounty for this
>
> http://fqa.9front.org/appendixb.html
I would like to add 50$ for this.
At the moment, I’m trying to understand how plan9/arm is implemented, to get an idea what needs to be done for plan9/arm64.
As far as I understand, /src/syscall/mksysnum_plan9.sh in go is used to get the information from /src/libc/9syscall/sys.h from plan9, using it in /src/syscall/zsysnum_plan9.go and at the beginning of /src/runtime/sys_plan9_arm.s.
/src/runtime/defs_plan9_arm.go is the information from /arm/include/ureg.h with getter and setter functions.
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.
Is there documentation about the go code itself, regarding the machine dependent parts?
And do you know where I can find the plan9 counterparts to some of the files listed above?
Thank you very much in advance!
Best regards,
sml
next prev parent reply other threads:[~2022-03-16 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 19:40 sml
2022-03-13 21:10 ` cinap_lenrek
2022-03-14 6:37 ` sml
2022-03-14 10:47 ` sml
2022-03-14 15:18 ` ori
2022-03-15 6:19 ` sml
2022-03-15 11:15 ` Philip Silva
2022-03-15 16:32 ` Kurt H Maier
2022-03-16 7:43 ` sml [this message]
2022-03-16 15:16 ` ori
2022-03-16 17:01 ` cinap_lenrek
2022-03-16 19:29 ` Steve Simon
2022-03-13 23:59 ` ori
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=983983D5-BCC6-4187-9F01-70C81C81ABE0@firstpost.pub \
--to=sml@firstpost.pub \
--cc=9front@9front.org \
/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).