tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] macos: new tcc command line option?


From: Christian Jullien
Subject: Re: [Tinycc-devel] macos: new tcc command line option?
Date: Sun, 12 Jul 2020 08:05:46 +0200

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 differences. This why clang is also mostly compatible with gcc.

If tcc is not, at least, partially compatible with gcc, it means very few source packages will not compile with tcc.

This dramatically lowest the interest of tcc.

 

C.

 

From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange.fr@nongnu.org] On Behalf Of ian
Sent: Sunday, July 12, 2020 07:21
To: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] macos: new tcc command line option?

 

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 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 simple to add and possibly revert later.

On Saturday, July 11, 2020, 08:09:07 AM GMT+3, Christian Jullien <eligis@orange.fr> wrote:

 

 

Hi maintainers,

 

As often, Apple reinvent the wheel and makes things differently.

Among other, clang handles shared libs .dylib with a different set of compiler options.

For example, -shared is replaced by –dynamiclib etc…

 

It means that a ./configure must test if it uses clang or tcc and adapt its compiler options.

 

Question: with proper #if/#endif do you allow me to handle clang specific options on macos?

 

FYI I currently see 4/5 options to add (or at least silently drop) to support tcc on macos with a better compatibility with clang.

 

C.

_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel



_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

--
-- sibian0218@gmail.com
-- Développeur compulsif


reply via email to

[Prev in Thread] Current Thread [Next in Thread]