[openbeos] What is special about GCC 3 ?!?

  • From: Mat Hounsell <mat_geek@xxxxxxxxxxxx>
  • To: Open BeOS <openbeos@xxxxxxxxxxxxx>
  • Date: Fri, 20 Sep 2002 17:36:49 +1000 (EST)

Long, long ago in the before time ...

There were no formal software standards and the informal ones were abused by
corporations attempting to gain market share. This meant that you could only
use the operating system's language, compiler and linker to develop

After a while the corporations realised there was a massive cost in maintaining
compilation systems with only negative results for the trouble.

Eventually it was relized that alllowing the user to develop as they wished
delivered a better return on investment. As such a standard was developed to
allow any C linker to link modules compiled by any/many C compilers.

C++ however is far more complex than C. It introduces issues of member layout,
virtual tables, RTTI, and name mangling, which of course every compiler does

While Intel developed their 64 bit CPU that relized that a common standard for
C++ would increase interest in their chip and improve their profit.

This new standard "http://www.codesourcery.com/cxx-abi"; has developed into a
new independant standard for C++ compilation.

GCC 3.2 implements this new standard and allows developers to compile and link
modules with any compiler that implements this standard.

It also allows compiler nuetral system libraries. In theory the versions of
OSBOS that are compiled to this standard will be compiler nuetral. Allowing the
YouBuet Compiler to be used with the system libraries.

From R2 it would be advised for us to use a standard compliant compiler, in the
long term it would reduce ABI issues.

http://mobile.yahoo.com.au - Yahoo! Messenger for SMS
- Always be connected to your Messenger Friends

Other related posts:

  • » [openbeos] What is special about GCC 3 ?!?