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 > <eli...@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 <mailto: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 -- -- sibian0...@gmail.com -- Développeur compulsif
_______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
