guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#26926: [PATCH] gnu: update Mes to 0.6.


From: Jan Nieuwenhuizen
Subject: bug#26926: [PATCH] gnu: update Mes to 0.6.
Date: Tue, 16 May 2017 23:33:29 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)

-----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 <address@hidden>
>> 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 <address@hidden> | 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-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]