Tcc 'mob' has became a project of many goals.

Some like it the way it is because it suits their purpose (K&R C would do, C89 
too).

Some try to use it for RISC-V compilation to avoid toolchains of pachydermic 
dimension (LLVM, GCC).

I wanted to have full C11 compliance because I dislike tcc hybrid-like nature 
of the feature set and standard support.

Let's says I "hoped" for tcc not to fall in the same demise than minix, but 
that's not my main quest in the end.

Some people in the list told me that tcc is quite beloved around, despite not 
having a clear versioning scheme.

I too wanted a "clarification" of tcc status, showing it being maintained, kept 
up to date and "relevant".

In the end it's grishka, the main maintainer in charge, who decide if a new 
release is worth the pain.

There are other similar compilers out there after all, even I use VBCC instead 
for my m68k developments :

http://www.compilers.de/vbcc.html

There are 8 billions people out there, I think if each one did his part, the 
world wouldn't be in the state it is.

Same for open source projects.

Regards.


----- Mail d'origine -----
De: Eyal Rozenberg <[email protected]>
À: david koch <[email protected]>, [email protected]
Envoyé: Fri, 13 Feb 2026 01:10:04 +0100 (CET)
Objet: Re: Re : [Tinycc-devel] The project seems to be missing a new release 
and/or a roadmap

Indeed, I was not aware of the history of past discussions. However - no 
user who does not 'mine' the mailing list is aware of that. So, My 
request and suggestion remains...

At the link, there is a thread about the criteria for releasing version 
1.0, and it is said that "fully passing conformance tests" is a 
necessary condition for that. I see that there was some discussion on 
alternative goals for a 1.0 version, e.g. being able to faithfully 
compile a working version of a suite of programs. Did you end up 
reaching a consensus? Also, even if you weren't - there is not even a 
proper table of missing/implemented/partial values for features by C 
standard. Here is GCC's:

https://gcc.gnu.org/projects/c-status.html

there are a lot more C99 features that are mentioned in the 
documentation for example. Why not duplicate this page, start by filling 
in what's already documented (either with the first implementing release 
or starting with "sometime before 0.9.27" to be made exact later), and 
proceed to the other features? And put that on the tinycc.org website, 
with links from savanna, the repo website(s), or even the README?


You suggested that I define a clear goal for the next version. Well, I'm 
not a TinyCC developer, so I don't feel it is my place to do that. But - 
here is a possible goal from a user's perspective: Endow the user base 
with the improvements to the compiler between 2017 and some point near 
the present - in the form of a release, which is of a stability/quality 
comparable or better than that of 0.9.27. Developers are able to just 
pull the latest head of the main branch and use it reasonably and 
carefully, but most (?) users typically limit themselves to releases, as 
head commits sometimes contain glaring ephemeral issues introduced 
recently by mistake, or new features that are semi-broken. And that is 
obviously much less likely when you create a release branch and freeze 
it for new features, landing only bug fixes on it, for a while.


And even a decision about a roadmap or upcoming minor release is not 
made soon - it is still important to update the website with where 
things stand: Describe how the project governance works now (as opposed 
to the self-disciplined free push policy), mention some key active 
contributors perhaps. I see some of this in:

https://www.mail-archive.com/[email protected]/msg11284.html

and of course, the README still has Fabrice Bellard signing as what seem 
the single maintainer/developer.

Respectfully,
Eyal

On 09/02/2026 16:08, [email protected] wrote:
> Hello you,
> 
> this discussion **again** ?
> 
> https://www.mail-archive.com/[email protected]/msg11276.html
> 
> Define a clear goal for the next version and do your part to make tcc reach 
> it.
> 
> If you followed list closely, you'd seen there are still many bugs.
> 
> Yes, I'm old and grumpy.
> 
> David
> 
> 
> ----- Mail d'origine -----
> De: Eyal Rozenberg via Tinycc-devel <[email protected]>
> À: TinyCC Development Mailing List <[email protected]>
> Cc: Eyal Rozenberg <[email protected]>
> Envoyé: Mon, 09 Feb 2026 14:50:40 +0100 (CET)
> Objet: [Tinycc-devel] The project seems to be missing a new release and/or a 
> roadmap
> 
> Hello all,
> 
> I am not a tinycc contributor (and only rarely a user). I joined the
> mailing list to relay a sentiment of the "casual user".
> 
> So, I'm looking at the project's:
> 
> Website       https://tinycc.org
> repo-website  https://repo.or.cz/w/tinycc.git
> README
> 
> and here is what I notice:
> 
> * The last release, 0.9.27, was made 9 years ago, in 2017. Nearly a
> decade. This, while development and maintenance seems to be continuing
> unabated :-)
> * The website has not been updated since 2018.
> * None of the three venues give an up-to-date description of the project
> in the  structural/organizational sense, i.e. how are decisions and and
> by whom.
> * None of the three venues contain a roadmap, outlook or plan for future
> activities, specifically a new release.
> 
> So, I would like to ask that you consider:
> 
> * Preparing/committing a prospective roadmap regarding future work and
> release schedule for the project.
> * Making a 0.9.28 or 0.10.0 (or 1.0 ?) release, soon.
> * Updating all three venues with some or or most of that information.
> 
> 
> Respectfully,
> 
> Eyal Rozenbergx       
> 
> _______________________________________________
> 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