***** Borland is the fastest compiler, has good language support, and does not shame itself in any other regard. It
has value to contribute in its good warnings. However, it seems to share VC++'s predilection for internal compiler
errors (ICES) when things get too hards for it, which I found annoying.
***** GCC has the best language support, which is commensurate with its having the widest collaboration of any
open-source (and probably commercial as well) compiler in the business. However, it may also account for its
poor efficiency characteristics. On my tested scenario, it proved to be the slowest compiler, and produced the
slowest and fattest code.
***** For speed of generated code - which is often the most important factor --- Intel reigns supreme.
***** VC++ produces the smallest code, is quick to compile, and does well in the performance of generated code
( though it's still way off Intel's performance).
All C++ professional and organizations should use more than one C++ compiler at all times. No compiler provides
all the possible useful warnings, so compiling with multiple compilers affords much more comprehensive coverage.
Furthermore, there's nothing better for making your code port-prepared than making it work with more than one
compiler. Particularly bad in this regard have been the Borland and VC++ compilers.
has value to contribute in its good warnings. However, it seems to share VC++'s predilection for internal compiler
errors (ICES) when things get too hards for it, which I found annoying.
***** GCC has the best language support, which is commensurate with its having the widest collaboration of any
open-source (and probably commercial as well) compiler in the business. However, it may also account for its
poor efficiency characteristics. On my tested scenario, it proved to be the slowest compiler, and produced the
slowest and fattest code.
***** For speed of generated code - which is often the most important factor --- Intel reigns supreme.
***** VC++ produces the smallest code, is quick to compile, and does well in the performance of generated code
( though it's still way off Intel's performance).
All C++ professional and organizations should use more than one C++ compiler at all times. No compiler provides
all the possible useful warnings, so compiling with multiple compilers affords much more comprehensive coverage.
Furthermore, there's nothing better for making your code port-prepared than making it work with more than one
compiler. Particularly bad in this regard have been the Borland and VC++ compilers.
