>Martin Bochnig wrote:
>If you would drop Studio and would globally switch to gcc, you would
>not only save lots of R&D, but additionally you could relatively
>easily support cross-compilation (x86/SPARC, also on LinUX etc ... ).
The only thing is that in this case "one glove does not fit all" as in
Sun Studio mainly is used for performance gains and debugging analysis.
I've used Sun Studio and GCC for many years so I agree that Sun Studio
has many shortcomings - but it does a good job when it "works" as expected.
Sun has fixed many of those "shortcomings" in Sun Studio but due to many
reasons may not be on the same level as other compilers in other areas.
Does that mean we should run to using Clang/LLVM??? No.
Oh yes, GCC is not perfect either - but developers have adapted to it
over many years and it becomes a "candy pulling babyfight" to incorporate
adoption to another major compiler in short migration order.
GCC was chosen by Sun as the compiler to use for porting FOSS-based projects to
Sun Solaris/OpenSolaris. This led to the GCCFSS hybrid project
and several OpenSolaris distributions using solely GCC for their
development purposes. More FOSS developers and students are trained on
GCC versus Sun Studio and Clang/LLVM. So, it is better that we build from a
toolbox of tools rather than trying to build a house with only a screwdriver
and no screws or blueprint.
~ Ken Mays
