Switching the default for -fabi-version

[Gabriel Dos Reis]

law@redhat.com writes:

| In message <1066811338.4002.6.camel@minax.codesourcery.com>, Mark Mitchell writ
| es:
|  >
|  >> which are not very clear (may vs. will) and omitting of a reason (in case
|  >> of the second warning). So to say, if I can still specify -fabi-version=0
|  >> I'm happy with changing. But you could try to make sure you dont break
|  >> libstdc++ compatibility with this change?
|  >
|  >This is the point everyone seems to be missing: libstdc++ compatibility
|  >is *already* going to break in GCC 3.4.
| But as you know, not everyone uses libstdc++ ;-)  

:-)

[...]

|  >The only situation where the change I'm proposing would matter is when
|  >you're using the new compiler with the old library.  That probably won't
|  >work anyhow -- since, for example, the new parser probably can't handle
|  >the old headers.
| I wasn't aware of this.

This is mostly related to name lookup issue and parsing errors.
While working on the parser, Mark made many corrections to the
headers.

The name lookup business can lead to different functions being called.

|  >But, if, somehow, it would work without the change, it will also work
|  >with the change -- provided you add -fabi-version=1 to your command
|  >line.
| That may ultimately be the answer.  Bump up and allow folks who need it
| to explicitly ask for the old ABI.  

yes.  I think that option has always been available since the last
3.1.1 -> 3.2 psychodram.

-- Gaby