From: <Jeremiah@pdp10.guru>
To: guile-user@gnu.org
Subject: RE: You missed my later work
Date: Fri, 31 Mar 2017 16:28:25 -0400 [thread overview]
Message-ID: <E1cu39l-0007yL-1z@ITSx00.pdp10.guru> (raw)
I had recently watched your FOSDEM talk https://fosdem.org/2017/schedule/event/guixsdbootstrap/ [fosdem.org]
Which you seem to have confused my hex assembler as an end in itself, rather than the first step in Stage0
Basically, I decided to steal a good idea from the C and pascal languages (o-code and p-code specificly)
Define a trivial to implement virtual machine (vm.c vm.h vm_decode.c and vm_instructions.c [optionally tty.c and/or dynamic_execution_trace.c but neither is required])
Who's entire instruction set is define in ISA_HEX_Map.org
That way all platforms can independently verify every step
Looking at your work, I can't help but wonder if we might be making that bootstrap step harder than it has to be.
What if we converted my lisp interpreter into a lisp compiler? Could that simplify your initial bootstrap?
Since instead of trying to do the full C compiler in scheme in a single step, we could do:
Primitive_scheme -> minimal_scheme -> full_scheme -> done
What do you think?
Jeremiah Orians
State of Michigan
Cell phone: (517) 896-2948
> -----Original Message-----
> From: Jan Nieuwenhuizen [mailto:janneke@gnu.org]
> Sent: Tuesday, March 28, 2017 5:09 PM
> To: Orians, Jeremiah (DTMB) <OriansJ@michigan.gov>
> Subject: Re: You missed my later work
>
> Orians, Jeremiah (DTMB) writes:
>
> Hi!
>
> Thanks for reaching out.
>
>> https://github.com/oriansj/stage0 [github.com]
>
>> It includes everything one needs, starting from a hex monitor to a primitive lisp for
>> a very portable VM specification (Which is also included and implemented)
>
> You implemented a LISP? I'll have to look into it! I looked at your
> amazing self hosting hex assembler and that's what got me going on
> implementing Mes.
>
> What do you mean by `You missed my later work?,' are you referring to
> some event? I have been very busy working on Mes: a scheme intepreter
> written in C, that can execute a Scheme program which is a C compiler
> that can compile itself. I'm almost done: Guile can run the C compiler
> in Scheme, Mes still fails.
>
> Have you been following Mes? I'm wondering if we can/should work
> together somehow. It seems we very much are working towards a similar
> goal.
>
> Greetings, janneke.
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org [lilypond.org]
> Freelance IT http://JoyofSource.com [JoyofSource.com] | Avatar® http://AvatarAcademy.nl [AvatarAcademy.nl]
next reply other threads:[~2017-03-31 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 20:28 Jeremiah [this message]
2017-03-31 21:48 ` You missed my later work Jan Nieuwenhuizen
2017-03-31 23:17 ` Jeremiah
2017-04-27 12:55 ` Jan Nieuwenhuizen
2017-04-27 23:51 ` Matt Wette
2017-05-01 1:02 ` Jeremiah
2017-05-02 6:17 ` Next steps for Mes, stage0+? -- " Jan Nieuwenhuizen
2017-05-02 18:26 ` Jeremiah
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1cu39l-0007yL-1z@ITSx00.pdp10.guru \
--to=jeremiah@pdp10.guru \
--cc=guile-user@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).