From: Ian Lance Taylor <iant@google.com>
To: Stuart Brooks <stuartb@cat.co.za>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Compatibility between g++ 4.1 and 4.2
Date: Sun, 20 Jan 2008 16:13:00 -0000 [thread overview]
Message-ID: <m33asvhyc3.fsf@localhost.localdomain> (raw)
In-Reply-To: <47904E0C.2000406@cat.co.za>
Stuart Brooks <stuartb@cat.co.za> writes:
> I was wondering if anyone could tell me whether C++ libraries compiled
> with gcc 4.2 are compatible with gcc 4.1 and vice versa. From
> http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html I see that:
> "Starting with GCC 3.2, GCC binary conventions for C++ are based on
> a written, vendor-neutral C++ ABI "
> and:
> "We have tried hard to provide a stable ABI that will be compatible
> with future GCC releases, but it is possible that we will encounter
> problems that make this difficult"
>
> Does this mean I should have no problems?
In general, yes. Assuming there are no bugs. Also see the
-fabi-version option.
Be aware that there was a bug in gcc 4.2.1 which was not in gcc 4.2.0
or gcc 4.2.2: the virtual table layout of the std::type_info class was
accidentally reordered.
Ian
prev parent reply other threads:[~2008-01-18 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 1:39 Stuart Brooks
2008-01-20 16:13 ` Ian Lance Taylor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m33asvhyc3.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=stuartb@cat.co.za \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).