On Fri, 2026-11-20 at 23:40 +0000, Detlef Riekenberg via Tinycc-devel
wrote:
> 
> 
> Hi TinyCC users, hi grischka.
>  
> As already mentioned many times, i think, that tinycc needs a
> release.
>  
> I asked for a release several times, but only grischka can do it, as
> he owns the project at repo.or.cz
> and he had the contact to Fabrice at the last release.
>  

I definitely agree that TinyCC needs a release, and I really think that
the next release should be in source form (e.g. as some tarball). I am
French and a Linux only open source software developer.

I would like to mention a few things:

1. On Debian/Trixie (and Linux Mint 22.3) the packaged tinycc is old.
% /usr/bin/tcc --version
tcc version 0.9.27 (x86_64 Linux)

2. TinyCC has several important features:
a. Its source code is small (compared to that of gcc.gnu.org) and can
be studied easily. So it is educational.
b. TinyCC runs fast, and can compile C code inside memory using
tcc_compile_string. This makes TinyCC very useful in many software
generating code at runtime (if they choose to generate it as some C
code (see https://arxiv.org/abs/1109.0779 for ideas)
However, current compilers and computers are fast enough to be able to
fork another compilation on generated C code in temporary files, with
that compilation generating a dlopen-able plugin. (for an example,
see https://github.com/bstarynk/misc-basile/blob/master/manydl.c ...)
c. We all know that compared to much bigger C compilers (gcc.gnu.org or
clang.llvm.org) used with optimization flags TinyCC produces slower
code.

Regarding machine code generation there are other approaches (non-
compatible with TinyCC), e.g. asmjit.com or libgccjit in GCC, and GNU
lightning. And the lisp compiler SBCL.org also generates code in
memory.
GNU lightning is an interesting alternative (it does not accept C
syntax like TinyCC), since like TinyCC it is designed to generate
quickly machine code in memory.  

3. Most Linux distributions are not compiled with TinyCC (I do know
about Fabrice experimentation on compiling the Linux kernel on the fly
with TinyCC)

4. TinyCC do have some "competitors". The one I did try was
nwcc https://nwcc.sourceforge.net/ (like tinycc, quickly compiling
without optimizing it C code). https://github.com/ffashion/chibcc is
also one.

5. My wish is that TinyCC would provide some more internal API, e.g.
something constructing (in memory) an abstract syntax tree; perhaps the
libgccjit interface might be inspirational.... 

5. Another suggestion is to have TinyCC cooperating with frama-c.com
(it is an open source static analyzer using some specific comments in
the analyzed C code).


I am interested (since teaching Linux programming) to understand what
rather big open source software coded in C can be compiled
(successfully) using TinyCC (on Linux AMD64) (I believe that ocaml.org
is one of them).

Thenks for reading (I am French and born in 1959)
-- 

Basile STARYNKEVITCH <[email protected]>
8 rue de la Faïencerie http://starynkevitch.net/Basile/ 
92340 Bourg-la-Reine https://github.com/bstarynk
France https://github.com/RefPerSys/RefPerSys
https://orcid.org/0000-0003-0908-5250
_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to