This is the mail archive of the
mailing list for the GCC project.
Re: C++ ABI Issues
- From: Per Bothner <per at bothner dot com>
- To: Devang Patel <dpatel at apple dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Tue, 27 Aug 2002 12:02:49 -0700
- Subject: Re: C++ ABI Issues
- References: <644F3EB1-B9E5-11D6-9BD0-00039310EDEA@>
Devang Patel wrote:
On Tuesday, August 27, 2002, at 09:49 AM, Mark Mitchell wrote:
Based on the very clear consensus from the various distributors, I'm
going to implement patches today that add the warnings and
I hope there will be an option to disable warnings.
I hope there will be an option to enable warnings.
The default should be no warnings.
Since we don't have multi-vendor library compatibility
(or are both HP and Intel using libstc++?), incompatibility
with other compilers is a theoretical concern. It should not
cause the compiler to complain about perfectly valid code.
Yes, it means the code will be binary incompatible with
future versions of G++, but that is likely to be true for
most non-trivial C++ code. This assumes that we will not
change the default ABI, for quite a while, until there is
a *really* good reason to change, one good enough to
force *everybody* to re-compile.