From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: guix-devel@gnu.org, guile-user@gnu.org, epsilon-devel@gnu.org,
bootstrappable@freelists.org
Subject: Re: Mes 0.10 released
Date: Tue, 12 Sep 2017 07:15:13 +0200 [thread overview]
Message-ID: <877ex4pkf2.fsf@gnu.org> (raw)
In-Reply-To: <87shfsevm7.fsf@web.de> (Arne Babenhauserheide's message of "Tue, 12 Sep 2017 00:08:18 +0200")
Arne Babenhauserheide writes:
> Jan Nieuwenhuizen <janneke@gnu.org> writes:
>> Arne Babenhauserheide writes:
>>> Jan Nieuwenhuizen <janneke@gnu.org> writes:
>>>> I am pleased to announce the release of Mes 0.10, representing 82
>>>> commits over 6 weeks. Mescc now compiles a bootstrappable-modified
>>>> TinyCC into a mes-tcc that in turn can successfully compile a trivial
>>>> C program.
>>>
>>> Nice! How big are your changes to TinyCC?
>>
>> $ gl| head -30
>> 6773110e lotsa debug printing
>> 429e4366 bootstrappable: workaround mescc bugs.
>> 5881b4cd bootstrap build scripts
>> 2712a934 bootstrappable: struct by value assign.
..
>> For details, see
>>
>> [8] https://gitlab.com/janneke/tinycc
>>
>> TinyCC uses (imho) unnecessarily complex C constructs. Therefore it is (imho)
>> not too well suited as a bootstrap dependency, at least not in an
>> unpatched state.
>
> It still works with GCC, right?
Yes. Luckily, GCC can still handle simple C constructs ;-)
When running i686-unknown-linux-tcc and mes-tcc to compile a trivial C
program, the output produced by `lotsa debug printing' from both
compiler runs is now identical, as is the resulting ELF binary.
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | AvatarĀ® http://AvatarAcademy.com
next prev parent reply other threads:[~2017-09-12 5:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 20:29 Mes 0.10 released Jan Nieuwenhuizen
2017-09-11 17:14 ` Arne Babenhauserheide
2017-09-11 17:29 ` Jan Nieuwenhuizen
2017-09-11 22:08 ` Arne Babenhauserheide
2017-09-12 5:15 ` Jan Nieuwenhuizen [this message]
2017-09-12 17:08 ` Arne Babenhauserheide
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=877ex4pkf2.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=arne_bab@web.de \
--cc=bootstrappable@freelists.org \
--cc=epsilon-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@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).