GCC2 merging (was "native language support now available")

[Jason Merrill]

>>>>> Alexandre Oliva <oliva@dcc.unicamp.br> writes:

 > These were introduced as a large patch, submitted from someone, but I
 > believe new improvements that might cause long-term instability would
 > be introduced in egcs as separate branches or as features that can be
 > enabled by command-line arguments or configure switches, disabled by
 > default until the feature stabilizes.

 > This is exactly what is happening within the C++ front-end: the new
 > name mangling mechanism (-fsquangle), the empty base class
 > optimization (-fnew-abi) and the std namespace compliance
 > (-fhonor-std) are all in this stage of development, but they can all
 > be used in full releases, as long as the user (hacker) knows that they
 > are not as fully tested as the stable part of the compiler.

FWIW, these are currently options that are off by default not because they
are immature, but because they would break binary compatibility; we're
saving them up to switch over all at once.

Jason