From: Arne Babenhauserheide <arne_bab@web.de>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: on bootstrapping: first Mes 0.3 released
Date: Tue, 13 Dec 2016 23:43:11 +0100 [thread overview]
Message-ID: <87shprpi0w.fsf@web.de> (raw)
In-Reply-To: <87lgvku6jq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Jan Nieuwenhuizen writes:
> Arne Babenhauserheide writes:
>> How do you compile the interpreter?
>
> The current interpeter I consider to be a prototype in C; I use gcc.
> However, HACKING mentions two ways forward
>
> ** Move mes.c into hex?
> One idea is to use OrianJ's amazing self-hosting
> [[https://github.com/oriansj/stage0][stage0]] hex assembler and
> minimal bootstrap binaries and rewrite the mes.c core to directly
> bootstrap into Scheme.
This seems to be the strongest option, but also very expensive. And only
useful if it becomes a step on the way to compile GCC (the goal of
stage0).
> ** Rewrite mes.c and generate hex?
> Another idea (thanks Rutger!) is to rewrite the mes.c core in a
> C/Assembly variant and have mescc produce the simple, annotated
> bootstrap binary.
>
> Possibly you have an even better idea? I am choosing to explore the
> latter first: work on the compiler backend and write the interpreter in
> its Assembly/C-like s-expressions.
I think the C/Assembly variant sounds better — maybe written in simple
enough style to be compiled by stage0 before that can compile GCC.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-12-13 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 21:10 on bootstrapping: first Mes 0.3 released Jan Nieuwenhuizen
2016-12-12 22:17 ` Arne Babenhauserheide
2016-12-12 22:27 ` Jan Nieuwenhuizen
2016-12-13 22:43 ` Arne Babenhauserheide [this message]
2016-12-16 16:21 ` Christopher Allan Webber
2016-12-20 7:58 ` Jan Nieuwenhuizen
2016-12-19 16:40 ` Ludovic Courtès
2016-12-25 15:11 ` Jan Nieuwenhuizen
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=87shprpi0w.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=janneke@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).