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
