From: Ian Lance Taylor <iant@google.com>
To: mario guerra <emailformario@yahoo.com>
Cc: mario guerra <emailformario@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: supporting multiple versions of GCC with a single shared object release?
Date: Wed, 15 Apr 2009 17:40:00 -0000 [thread overview]
Message-ID: <m34owpvmqw.fsf@google.com> (raw)
In-Reply-To: <340697.63416.qm@web34805.mail.mud.yahoo.com> (mario guerra's message of "Wed\, 15 Apr 2009 10\:13\:38 -0700 \(PDT\)")
mario guerra <emailformario@yahoo.com> writes:
> --- On Tue, 4/14/09, Ian Lance Taylor <iant@google.com> wrote:
>> The C++ compiler/library is supposed to have a stable ABI
>> as of gcc 4.0
>> and later. For earlier versions, you pretty much do
>> have to do a build
>> for each version.
>
> If we built our simulator with 4.x, wouldn't that potentially break
> some of our third party vendors who are still using some variant of
> 3.x? The 4.x library isn't backwards compatible, is it?
No, the 4.x library is not reliably backward compatible. Actually it
may be backward compatible to 3.4, but not before that. For earlier
versions you will still have to do a build for each version.
Ian
next prev parent reply other threads:[~2009-04-15 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 17:13 mario guerra
2009-04-15 17:40 ` Ian Lance Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-17 14:55 mario guerra
2009-04-17 15:30 ` Ian Lance Taylor
2009-04-15 17:09 mario guerra
[not found] <5480d0a80904141452g45324a9ch68c1e1a6e5e51904@mail.gmail.com>
2009-04-14 22:02 ` mario guerra
2009-04-14 22:09 ` Brian Budge
2009-04-14 22:21 ` Ian Lance Taylor
2009-04-15 15:09 ` John Fine
2009-04-16 17:06 ` Andrew Haley
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=m34owpvmqw.fsf@google.com \
--to=iant@google.com \
--cc=emailformario@gmail.com \
--cc=emailformario@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
/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).