This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: ABI/compatibility details? (egcs -> gcc 2.95 -> future?)
- To: pfeifer at dbai dot tuwien dot ac dot at
- Subject: Re: ABI/compatibility details? (egcs -> gcc 2.95 -> future?)
- From: "Martin v. Loewis" <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Date: Sat, 9 Oct 1999 13:05:42 +0200
- CC: mark at codesourcery dot com, mrs at wrs dot com, gcc at gcc dot gnu dot org
- References: <Pine.GSO.4.10.9910090045070.4748-100000@alphard.dbai.tuwien.ac.at>
> I believe there is one major difference: The (reported) problems related
> to -fstrict-aliasing do not show up immediately during compiliation, while
> an ABI change immediately will show up during linking.
Well, the "empty base class optimization" is not linkage-safe: linking
code compiled with and without it will result in crashes or other
strange behaviour. Therefore, activating that must be combined with
activating other ABI changes that do result in linkage errors (such as
squangling, or vtable thunks).
Regards,
Martin