From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: GSoC 2021 project ideas
Date: Tue, 09 Feb 2021 00:34:57 +0000 [thread overview]
Message-ID: <37dc6806-7973-4e7f-ae6c-262a3f398feb@www.fastmail.com> (raw)
In-Reply-To: <86r1lrtrgo.fsf@cmarib.ramside>
On Sun, Feb 7, 2021, at 10:59 PM, cigar562hfsp952fans@icebubble.org wrote:
>
> That's a brilliant idea: a "Dis" assembler for Plan 9, to compile (well,
> assemble, really) Dis code to binaries for the host architecture. The
> Dis architecture was specifically designed to make it easy to map the
> Dis machine to the underlying architecture. But... the binary interface
> would have to be the Plan 9 one, so the proper place to do such assembly
> would be on Plan 9. If it were an extension of Inferno's JIT, it would
> have to track changes made to Plan 9. Since Dis is stable and
> standardized, it makes more sense for a Plan 9 tool to track Dis than
> the other way around.
Thanks! I'm far from being an expert in the generation of object files, so I'll bow to your knowledge there.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T39aec8f3f9d8503d-M1952db434f371b6dab1c94e3
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-02-09 0:35 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:23 [9fans] Plan 9 Applying to GSoC 2021 Anthony Sorace
2021-02-01 0:31 ` ~vidak
2021-02-01 9:35 ` sirjofri
2021-02-01 11:07 ` svaderaa
2021-02-01 11:26 ` Bakul Shah
2021-02-02 1:15 ` raingloom
2021-02-01 7:16 ` [9fans] GSoC 2021 project ideas (WAS: Re: Plan 9 Applying to GSoC 2021) cigar562hfsp952fans
2021-02-01 20:46 ` Steve Simon
2021-02-03 14:14 ` Ethan Gardener
2021-02-01 21:47 ` [9fans] GSoC 2021 project ideas sirjofri
2021-02-03 14:07 ` Ethan Gardener
2021-08-06 16:25 ` Jack Johnson
2021-08-19 21:06 ` unobe
2021-09-20 4:52 ` [9fans] " cigar562hfsp952fans
2021-09-20 5:08 ` Conor Williams
2021-09-20 5:11 ` vidak
2021-09-20 15:02 ` ori
2021-09-20 5:43 ` [9fans] " Dave Eckhardt
2021-09-20 7:51 ` Ethan Gardener
2021-09-20 8:23 ` hiro
2021-09-20 8:37 ` Conor Williams
2021-09-20 8:39 ` Conor Williams
2021-09-20 8:45 ` Conor Williams
2021-09-20 8:52 ` Conor Williams
2021-09-20 8:58 ` Conor Williams
2021-09-20 11:06 ` Conor Williams
2021-09-21 9:01 ` Ethan Gardener
2021-09-20 11:05 ` sirjofri
2021-09-20 11:08 ` Conor Williams
2021-09-20 14:01 ` sirjofri
2021-09-21 9:25 ` Ethan Gardener
2021-02-02 8:29 ` [9fans] GSoC 2021 project ideas (WAS: Re: Plan 9 Applying to GSoC 2021) tlaronde
2021-02-03 15:07 ` Ethan Gardener
2021-01-19 11:08 ` pouya+lists.9fans
2021-02-03 18:58 ` Ethan Gardener
2021-02-06 2:17 ` David Arroyo
2021-02-03 18:26 ` ori
2021-02-03 23:31 ` Skip Tavakkolian
2021-02-05 16:42 ` Ethan Gardener
2021-02-07 22:59 ` [9fans] Re: GSoC 2021 project ideas cigar562hfsp952fans
2021-02-09 0:26 ` Steve Simon
2021-02-09 1:59 ` [9fans] " Jeff Sickel
2021-02-09 0:34 ` Ethan Gardener [this message]
2021-02-02 5:30 ` [9fans] Plan 9 Applying to GSoC 2021 ori
2021-02-02 10:40 ` [9fans] Project idea (was: Plan 9 Applying to GSoC 2021) sirjofri
2021-02-02 16:07 ` [9fans] Re: Plan 9 Applying to GSoC 2021 Jeff Sickel
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=37dc6806-7973-4e7f-ae6c-262a3f398feb@www.fastmail.com \
--to=eekee57@fastmail.fm \
--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).