I personally, fwiw, stopped updating my port some months ago.
We had "many additions" followed by "grishka removals" several
times lately, and so i wait for the next of the latter before
i update that again.

I actually, again fwiw, would support a release, even though
i continue to use direct git-based snapshots for the port.  But
  https://repology.org/project/tcc/versions
does not look so good, and quite some people put considerable
effort into tcc, .. even compared to the git-snap ones there.

Regarding the younger additions.
I already didn't like the "restrict" thing, .. granted i never
liked nor used "restrict" myself.  That optional stuff is even
more weird, i for one "surely" will never use that myself.

Per se i do not have that much against such additions, but am of
the opinion that such diagnostics should be optional for tcc.  Ok,
compile-time, ie entirely stripped, is possibly too much trouble,
but if i want "real" such checks i run gcc and/or clang (and/or
Coverity even, pre-release; do not get paid for that, really).

tcc should be as small and as fast as possible, that is the thing
for me.  I mean, heck, there are people with 64 processor ripper
machines and more, if they do "$CC -j $(nproc)", you know, they
get more speed than myself plus the better diagnostics.  That is
not what i use tcc for.

Thanks everybody for spending time and effort on this project!

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

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

Reply via email to