From: Arne Babenhauserheide <arne_bab@web.de>
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.10 released
Date: Tue, 12 Sep 2017 00:08:18 +0200 [thread overview]
Message-ID: <87shfsevm7.fsf@web.de> (raw)
In-Reply-To: <87fubtp2il.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]
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?
>
> About this big:
>
> $ gl| head -30
> 6773110e lotsa debug printing
> 429e4366 bootstrappable: workaround mescc bugs.
> 5881b4cd bootstrap build scripts
> 2712a934 bootstrappable: struct by value assign.
> 54e9ae5b bootstrappable: constant pointer arithmetic.
> 10b7a57b bootstrappable: pointer arithmetic.
> 25f6dfa1 bootstrappable: mescc: use _start.
> 50af7c8c bootstrappable: gcc libraries, elf entry.
> d783ec19 bootstrappable: uint16_t in struct on heap.
> f0aed53b bootstrappable: nested foo ? bar : baz.
> 60a3181f bootstrappable: Complex field access.
> 13cc75c8 bootstrappable: str[r]chr (str, 0).
> fc977c55 bootstrappable: sizeof *type.
> 2ed23278 bootstrappable: for (;;).
> 7ab3f511 bootstrappable: Multi-line strings.
> 871dc3bb bootstrappable: foo = bar = baz.
> 9413c474 bootstrappable: switch (*foo = *++bar).
> a51c6757 bootstrappable: HAVE_BITFIELD.
> ca8aa2f4 bootstrappable: HAVE_FLOAT
> eff5bcf9 bootstrappable: char foo[][].
> 299e04fe bootstrappable: foo ()->bar.
> cb487ef6 bootstrappable: Comma operator.
> df8f57cf bootstrappable: Heterogeneous switch case.
> 4cd6da01 bootstrappable: Heterogeneous initializer list.
> 25d426a0 bootstrappable: Outline enums, structs, unions.
>
> 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?
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-09-11 22:08 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 [this message]
2017-09-12 5:15 ` Jan Nieuwenhuizen
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=87shfsevm7.fsf@web.de \
--to=arne_bab@web.de \
--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).