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

2020-07-12 Thread Christian Jullien
orange...@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"

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

2020-07-11 Thread ian
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

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

2020-07-11 Thread avih via Tinycc-devel
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

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

2020-07-10 Thread Christian Jullien
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