This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C++ ABI Issues
- From: Ziemowit Laski <zlaski at apple dot com>
- To: gcc at gcc dot gnu dot org
- Date: Tue, 27 Aug 2002 11:07:00 -0700
- Subject: Re: C++ ABI Issues
On Tuesday, Aug 27, 2002, at 10:13 US/Pacific, Benjamin Kosnik wrote:
I'll restrain my comments to one area only.
Please, let's use the versioning info that already exists. Currently,
the compiler ABI is tracked with __GXX_ABI_VERSION. For the 3.2.0
release, this value is 102.
If there is to be a -fabi=xxx switch, then please use this information.
The idea of having a "-fabi-newest" is completely relative and useless:
newest from what vantage point?
I agree; it would definitely make sense to say something like,
'-fabi-version=102'.
Alternatively, should ABI fixes become so frequent as to make rolling
__GXX_ABI_VERSION
each time impractical (hopefully not likely...), then perhaps we can
key off dates --
say, '-fabi-version=20020827' ?
Another question is whether proprietary compilers (HP aC++, etc.) also
support
__GXX_ABI_VERSION, or whether it would be better to pick a more, uh,
neutral macro
name? What immediately comes to mind after that is a "#pragma
abi-version ...."
directive. (I apologize if the ABI spec already addresses these
issues; I am not
intimately familiar with it.)
My 2 zlotys,
--Zem
--------------------------------------------------------------
Ziemowit Laski 1 Infinite Loop, MS 301-2K
Mac OS X Compiler Group Cupertino, CA USA 95014-2083
Apple Computer, Inc. +1.408.974.6229 Fax .5477