From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26926@debbugs.gnu.org
Subject: bug#26926: [PATCH] gnu: update Mes to 0.6.
Date: Tue, 16 May 2017 23:33:29 +0200 [thread overview]
Message-ID: <8760h05vx2.fsf@gnu.org> (raw)
In-Reply-To: <87k25g5zyi.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 16 May 2017 22:06:13 +0200")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ludovic Courtès writes:
>> Mes 0.6 for Guix. Nyacc is now unbundled. Mescc works with vanilla
>> Nyacc. Mescc behaves more like a regular C compiler and now passes
>> 33/55 tests of the tinycc test2 test suite.
>
> Woow, really impressive progress.
Thanks!
>> Mescc can also be used as a Nyacc C compiler backend for Guile (x86 only).
>
> I got stuck in a meta-circular attempt to understand the meaning of this
> sentence. What does this mean in very explicit terms? :-)
What I call Mescc is a Scheme program that can be executed (interpreted)
by Mes, but it can also be run by Guile. Like so:
guix package -i nyacc mes
guile -c '(use-modules (language c99 compiler)) (with-input-from-string "int main () {return printf (\"Hi Mescc\n\");}" c99-input->elf)' > a.out
chmod +x a.out
./a.out
=> Hi Mescc
Does this make it more explicit?
>> From f84c29fa5947051033d022dcb02496d8f8e14d28 Mon Sep 17 00:00:00 2001
>> From: Jan Nieuwenhuizen <janneke@gnu.org>
>> Date: Sun, 14 May 2017 11:35:30 +0200
>>
>>
> ^ extra line :-)
Weird I think this is a mailing thing, the commit looks fine.
>> + ,@(if (or (equal? (%current-system) "x86_64-linux")
>> + (equal? (%current-target-system) "x86_64-linux"))
>
> Note that %current-system is a “system type” like “x86_64-linux”
> whereas %current-target-system is a GNU triplet like
> “x86_64-linux-pc-gnu”. Thus, the second line should be
>
> (string-prefix? (%current-target-system) "x86_64-linux")
Ah...ok. As an aside: would we want to to change one of these names?
> OK with this change!
Yay!
> I’ve added you as a member of the group on Savannah so you can push it
> yourself. :-)
Great.
> Please read ‘HACKING’ for the details. Before pushing, can you reply to
> this message and sign your reply with the OpenPGP key that you’ll use
> to sign commits? Also please upload your OpenPGP key to Savannah.
Okay, great!
janneke
- --
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQTRDCIV/LL7b0kRcwqngbapL1xx1gUCWRtwKQAKCRCngbapL1xx
1gbuAJ9p6uqKDp2uyU4fyHKM/vsVtyFIRwCgkdokPA4GjklWThXuW5oeGgEWkSQ=
=w12i
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-05-16 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 16:11 bug#26926: [PATCH] gnu: update Mes to 0.6 Jan Nieuwenhuizen
2017-05-16 20:06 ` Ludovic Courtès
2017-05-16 21:33 ` Jan Nieuwenhuizen [this message]
2017-05-17 7:32 ` Ludovic Courtès
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=8760h05vx2.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=26926@debbugs.gnu.org \
--cc=ludo@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).