This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: -fnew-abi and C++? (was C++ and 2.95.1)
- To: David Edelsohn <dje at watson dot ibm dot com>, gcc at gcc dot gnu dot org
- Subject: Re: -fnew-abi and C++? (was C++ and 2.95.1)
- From: "George T. Talbot" <george at moberg dot com>
- Date: Mon, 23 Aug 1999 22:46:12 +0000
- Organization: Moberg Research, Inc.
- References: <9908232234.AA39992@marc.watson.ibm.com>
David Edelsohn wrote:
>
> If you use the -fnew-abi option of G++, you need to BUILD libgcc
> and libstdc++ with that option. -fnew-abi is not a runtime option that
> you can select arbitrarily and co-exist with the old ABI. The new ABI
> affects mangling of C++ symbols. This is why -fnew-abi is waiting for a
> lot of functionality before it is enabled, because it will break
> compatibility with old object files and libraries.
>
> David
OK. Thanks for the heads up. I was only doing it because I wanted
thread-safe exceptions, which Jason Merrill at Cygnus says I get when
compiling gcc with --enable-threads, so I don't need -fnew-abi after
all.
--
George T. Talbot
<george@moberg.com>