This is the mail archive of the
mailing list for the GCC project.
Re: C++ ABI Issues
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Joe Buck <Joe dot Buck at synopsys dot com>
- Cc: jh at suse dot cz (Jan Hubicka), phil at jaj dot com (Phil Edwards), mark at codesourcery dot com (Mark Mitchell), gcc at gcc dot gnu dot org
- Date: 27 Aug 2002 21:30:29 +0200
- Subject: Re: C++ ABI Issues
- Organization: CodeSourcery, LLC
- References: <200208271852.LAA28306@atrus.synopsys.com>
Joe Buck <Joe.Buck@synopsys.com> writes:
| > > It seems that even if it does, we can preserve libstdc++'s binary
| > > compatibility by adding a dummy field that exactly fills up any padding.
| > > This will make no difference in 3.2, and will force any compiler correctly
| > > implementing the ABI to match the 3.2 interface.
| > Sorr for jumping into discussion, but :0
| > What exactly will this bring us? libstdc++ is not only C++ library installed
| > in the system and it is one of the most easilly upgardable when reinstalling
| > compiler?
| But we don't want to have to bump the major version number, forcing people
| to have two library copies if they need to run old binaries. We want the
| new libstdc++ to work with old binaries, meaning that it supports the same
Then, a much more viable way to handle this is to have the compiler do