From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org, guile-user@gnu.org, epsilon-devel@gnu.org,
bootstrappable@freelists.org
Subject: Re: Mes 0.9 released
Date: Thu, 27 Jul 2017 09:54:34 -0500 [thread overview]
Message-ID: <874lty0w2d.fsf@dustycloud.org> (raw)
In-Reply-To: <87eft3e6ue.fsf@gnu.org>
Jan Nieuwenhuizen writes:
> I am pleased to announce the release of Mes 0.9, representing 107
> commits over 5 weeks. Mescc now compiles to a surprisingly readable
> stage0 M1 macro assembler output format. Also, mescc can now compile a
> modified TinyCC into a running [mostly segfaulting] executable. This is
> a major milestone as tcc can compile GCC.
Amazing stuff, Jan! You are doing the work of saints.
prev parent reply other threads:[~2017-07-27 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 12:11 Mes 0.9 released Jan Nieuwenhuizen
2017-07-26 20:09 ` Arne Babenhauserheide
2017-07-26 20:28 ` Jan Nieuwenhuizen
2017-07-27 14:54 ` Christopher Allan Webber [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://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=874lty0w2d.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=bootstrappable@freelists.org \
--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.
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).