Hi,
The reason is simple, you basically use 2 compilers:
- tcc for fast development cycle => CC=tcc ./configure; make
- gcc/clang for fast executable speed. => ./configure; make
You ever have played with autoconf, you know how difficult it is to manage
compiler differen
Hi Christian,
You're right, obviously.
The point were only "a mailing-list ain't a chat".
But, yes, obviously again, Avi did a great job !!
Kind regards.
ian
Le 11/07/2020 à 08:01, Christian Jullien a écrit :
>
> Hi Ian,
>
> Sorry for the inconvenience.
>
>
>
> We are talking to tinycc-deve
Hi there.
My point is "Why should tcc be gcc compatible ?"
Its main aim is to be faster, and "on the run" via #!/usr/bin/tcc.
IMHO, support too many options, and relevant code behind, is
anti-productive.
Regards.
Le 11/07/2020 à 11:10, avih via Tinycc-devel a écrit :
> I don't have proper gcc
I don't have proper gcc installed (via brew or macports), but I think it would
make sense to first check what gcc does and supports.
On the other hand, if it's only aliases to existing options, possibly which are
enabled only on OSX, then I don't think [m]any would object, and it should
be fairly
