From: Neil Jerram <neil@ossau.homelinux.net>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org, guile-user@gnu.org, epsilon-devel@gnu.org
Subject: Re: Mes 0.8 released
Date: Tue, 27 Jun 2017 00:34:43 +0100 [thread overview]
Message-ID: <20170626233443.5992527.53841.71118@ossau.homelinux.net> (raw)
In-Reply-To: <874lv359ct.fsf@gnu.org>
Hi Jan,
Thanks for your answer. I'm afraid I have no better ideas than the ones that you have listed - and in fact I wouldn’t have known about those ones either. I was just curious about what the next step would be.
It certainly seems to me like an interesting and worthwhile project.
Best wishes - Neil
Original Message
From: Jan Nieuwenhuizen
Sent: Monday, 26 June 2017 11:22
To: Neil Jerram
Cc: guile-user@gnu.org; guix-devel@gnu.org; epsilon-devel@gnu.org
Subject: Re: Mes 0.8 released
Neil Jerram writes:
Hi Neil!
> In your bootstrap path, what is the step after Mes? I guess it would
> be using mescc to compile some C program - but if that is right, which
> program?
Indeed. Short answer: I don't know. Do you have something in mind?
We haven't decided yet and are still exploring possibilities. We are
looking for the target that requires the least amount of work to get us
close the bootstrap path to gcc.
The most obvious candidate to compile with mescc is tinycc. rain1 has
worked with the tinycc and succeeded in compiling GCC 4.7.0 using
tinycc[0].
However, tinycc uses C constructs that mescc does not support [yet] and
libc functions that mescc's libc does not have.
So we are also considering other candidates such as 8cc, pcc, the ack,
cc500, gcc-2.95 (what about earlier gcc's?).
Another possible first target for Mescc could be libguile/eval.c ;-) and
develop a fork/sister of mescc as guilecc.
Greetings,
janneke
[0] https://lists.gnu.org/archive/html/tinycc-devel/2017-05/msg00103.html
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2017-06-26 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 16:49 Mes 0.8 released Jan Nieuwenhuizen
2017-06-26 9:22 ` Neil Jerram
2017-06-26 10:30 ` Jan Nieuwenhuizen
2017-06-26 23:34 ` Neil Jerram [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170626233443.5992527.53841.71118@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--cc=epsilon-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).