Re: [www] 3.2 ABI Compatibility issues

[Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>]

In article <ho8z3hvozh.fsf@gee.suse.de> you write:

> Here's the version that I committed.  Since I did not receive any
> feedback from the BSD folks, I removed most references to BSD.  If
> there's anything that other folks like to get added to this page,
> please speak up,

Can't speak for other folks but I only read the list once a day. ;-)

Thanks for documenting the issues.  I think it was OK to remove
detailed references to BSD.  If someone from a given BSD camp writes a
better description of how to maintain the C++ ABI for their system, it
could be added later.  I know about FreeBSD and could write it.
However, they haven't actually shipped a system with gcc 3.2 as the
system compiler thus anything would be tentative.  General comment: We
try to keep the defaults provided in the config.gcc thunk for the port
compatible with the system compiler.  Of course, we have failed to do
so in the past...

>+    <p>Configure GCC with these options:</p>
>+    <pre>
>+      --enable-threads=posix -enable-shared --enable-__cxa_atexit
>+    </pre>

It seems that some of the configuration that we gain from command line
options should be importable from the bootstrap compiler for native
builds perhaps keyed by a new option: --keep-abi-stable or somesuch.

E.g., it should be possible to learn the state of --enable-threads and
--enable-__cxa_atexit .  That seems better than forcing users to guess
how to build a new compiler with the most compatible C++ ABI.

Regards,
Loren
-- 
Loren J. Rittle, Principal Staff Engineer, Motorola Labs (IL02/2240)
rittle@labs.mot.com, KeyID: 2048/ADCE34A5, FDC0292446937F2A240BC07D42763672