|
From: | KHMan |
Subject: | Re: [Tinycc-devel] Using tinycc for full source bootstrapping |
Date: | Wed, 27 Sep 2017 09:41:20 +0800 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 9/27/2017 5:30 AM, address@hidden wrote:
On Sun, Sep 24, 2017 at 07:40:32PM +0200, grischka wrote:Also as source tcc is supposed to be C89, except maybe 'long long' and maybe some minor things here or there which we could change indeed if that is wanted (for example usage of compound initializers in arm-gen.c)[not a tinycc developer but using / depending on compiler bootstrapping] I would find it awesome if tinycc would restrict its source to C89.
2017 - 1989 = 28.Twenty-Eight Years. It would be kinda nice to move forward. Will we stick to C89 simply because of certain platforms that may never move forward? It's kinda like tying stones to one's legs. Or a lowest common denominator scenario.
Compilers written in C89 and understanding C99 hardly exist. This makes it hard to do a proper bootstrap from the ground with minimal dependency on existing binaries.
Could you give an example/examples where the starting point for a bootstrap is C89 for the foreseeable future? (Not trying to be a nitpick pest, but actual data points are usually a good thing, and tcc supports only a few processors, so it would be nice to know which one and what platform, or is it some future thing.)
I like Larry's posting. Item 1 can also be done by text processing. Or make a minimally functioning tcc C89 branch. Or bootstrap it the Pascal P4 way.
(Offtopic, but tightly related to the full bootstrapping: if tcc would also become relicensed to BSD-alike, this would not only make such deep bootstrapping easier but also allow getting to C99 without relying on GPL, which matters to some people and scenarios) Thanks for your work on tcc, Rune
-- Cheers, Kein-Hong Man (esq.) Selangor, Malaysia
[Prev in Thread] | Current Thread | [Next in Thread] |