From: sml <sml@firstpost.pub>
To: 9front@9front.org
Subject: Re: [9front] Go: "exec header invalid"
Date: Tue, 15 Mar 2022 07:19:03 +0100 [thread overview]
Message-ID: <A3F9279B-E42F-4150-BE7E-530E314DA9E9@firstpost.pub> (raw)
In-Reply-To: <ABC09CFE6237879493A60BE68CD510C7@eigenstate.org>
Again, thank you very much Ori.
This doesn't sound that simple to me, but it may be a good opportunity to understand both plan 9 and go a little better. If anyone knows of any helpful resources on this, I would appreciate a quick note.
Thank you and best regards,
sml
> Am 14.03.2022 um 16:18 schrieb ori@eigenstate.org:
>
> Quoth sml <sml@firstpost.pub>:
>> thank you cinap and Ori.
>>
>> what steps would be required to add support to armv8? would this be a good beginner project?
>>
>> if this is not the case, would it be possible to add a bounty?
>>
>> thank you and best regards,
>> sml
>>
>
> It wouldn't be particularly difficult -- arm64 support
> already exists for unix; the bulk of the work would be
> to add the plan 9 flavored assembly for doing system
> calls.
>
> Between a week for someone who's vaguely familiar with
> the code to a month or two for someone learning about
> the go internals as they go, at a guess.
>
next prev parent reply other threads:[~2022-03-15 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 [this message]
2022-03-15 11:15 ` Philip Silva
2022-03-15 16:32 ` Kurt H Maier
2022-03-16 7:43 ` sml
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=A3F9279B-E42F-4150-BE7E-530E314DA9E9@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).