You could also consider this project as well :

https://github.com/fuhsnn/slimcc

Regards.


----- Mail d'origine -----
De: Christopher Bazley <[email protected]>
À: [email protected]
Cc: draco <[email protected]>
Envoyé: Sun, 27 Sep 2026 15:53:17 +0200 (CEST)
Objet: Re: [Tinycc-devel] VERSION Number 1.0 - C11 vs. C99

Hi,

I think it's beneficial for the C programming language to have many
different front-ends: if taken into consideration by the C standard
committee, their good health should prevent the complexity of the
language from growing until it becomes impossible for all but the
biggest implementations to keep up with. If we end up in a situation
where it is impractical to implement a C2Y frontend in a compiler such
as TCC then I think that would be a great pity.  The world already has
a C-like language that is prohibitively complex to implement: it's
called C++.  I also question whether one could accurately describe TCC
as a C compiler under circumstances where it merely compiles the
output from another compiler.

A long time ago, people used to question whether C++ was a real
language in its own right, given the fact that the first C++ compiler
was a translator (called Cfront).  I expect the same attitude to
develop towards C23 and C2Y, if development of language frontends for
smaller compilers such as TCC is allowed to stagnate.

Instead of arguing in abstract terms about whether TCC should compile
C99, C11 or C23, I'd find it more enlightening to see a discussion of
which specific language features are thought to be too onerous to
implement, too complex to parse efficiently, or both (and more
importantly, why). That information could then be fed back to the C
standard committee.

Best regards,
Christopher Bazley

On Sun, Sep 27, 2026 at 7:22 AM Thiago Adams <[email protected]> wrote:
>
>
>
> Hi,
>
> Cake v0.15.4 can now be compiled with TCC.
>
> It has been tested on both Windows and macOS:
>
> tcc build.c && build
>
> Cake also targets TCC, meaning it can generate C code that TCC understands.
>
> Try cross compiling it in the Cake Playground:
> https://cakecc.org/playground.html
>
> or download:
>
> https://github.com/thradams/cake/releases/tag/v0.15.4
>
> Thiago
>
> On Tue, 12 Aug 2025 at 15:13, draco via Tinycc-devel 
> <[email protected]> wrote:
>>
>> Regarding C23 and language features:
>>
>> I would propose to use a proper C23 frontend, that can output "Ansi-C"
>> code that tcc can read.
>>
>> CAKE (https://github.com/thradams/cake) is maybe a good candidate.
>>
>> /quote Cake is a compiler front-end written from scratch in C, adhering
>> to the C23 language specification and beyond.
>>
>> It serves as a platform for experimenting with new features, including
>> C2Y language proposals, safety enhancements, and extensions such as
>> literal functions and defer statements.
>>
>> The current backend generates C89-compatible code, which can be
>> pipelined with existing compilers to produce executables.
>>
>> quote/
>>
>> I opened a discussion on Github with the author and he most immediatly
>> reacted and is doing some basic tests to see, if that kind of toolchain
>> (C23>cake>C89>tcc) could be implemented.
>>
>> So the much easier way would be to either use the tools as chain or, if
>> needed, implement a little console-main around both libraries that
>> processes and transports the necessary data to both libs.
>>
>> TinyCC can develop where it's best at and leave the language features to
>> the frontend.
>>
>> Regards
>>
>> Michael
>>
>>
>> Date: Tue, 12 Aug 2025 07:27:36 +0200
>> From: [email protected]
>> To: [email protected]
>> Subject: Re: [Tinycc-devel]  Re : Re: VERSION Number 1.0 - C11 vs.
>>         C99
>> Message-ID: <aJrQyLaF3o9LO1ps@localhost>
>> Content-Type: text/plain; charset=us-ascii
>>
>> On Mon, Aug 11, 2025 at 01:31:45PM -0700, Charles Lohr wrote:
>>
>> It is crucial for TCC to remain as simple, fast, and have the smallest
>> footprint possible.
>>
>> >   ...
>> >> Mature codebases already use
>> >> compiler-specific work-arounds and tweaks, so being "fully C11
>> >> compliant" doesn't actually buy you anything.
>> >   ...
>> >> And for my purposes is a
>> >> strict loss of suitability (because of the added code burdin).
>> >   +1 to the whole text.
>> >
>> > There are of course also codebases which deliberately assume a specific
>> > advanced language version or even a specific implementation of the
>> > toolchain, but they are by their choice and their design not the target
>> > area of Tinycc, as long as "tiny" is rightfully kept in the name.
>> >
>> >> I urge you please do not become obsessed with some sort of
>> >> completionist death march.
>> > Well said, thank you Charles.
>> >
>> > /tccm
>> >
>>
>> _______________________________________________
>> Tinycc-devel mailing list
>> [email protected]
>> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
>
> _______________________________________________
> Tinycc-devel mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel

_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to