Forgot to note

[Daniel Berlin <dberlin@redhat.com>]

When the C++ abi moves to the new-abi, I can't fix stabs support
without either adding a whole bunch of cruft, or making it not support
the old ABI.

This is because things like gdb_mangle_name have to be changed to
handle the new mangling scheme.
So I have to either detect whether we have old-abi or new-abi
somewhere, and then add a whole bunch of "if gnu-new-abi" type
statements, or stop supporting the old abi for stabs/C++.

Currently, the consensus on gcc seems to be that linux should move to
dwarf2 before 3.0 releases, which would mean that stopping support for
new-abi/stabs would also be an option.

DWARF2 will work fine with either ABI automatically.

What should we do?
Not support new-abi/stabs?
Not support old-abi/stabs?
Support both? (this is a not insignificant amount of work).

--Dan