From: Ian Lance Taylor <iant@google.com>
To: mario guerra <emailformario@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: supporting multiple versions of GCC with a single shared object release?
Date: Tue, 14 Apr 2009 22:21:00 -0000 [thread overview]
Message-ID: <m3ws9m27wu.fsf@google.com> (raw)
In-Reply-To: <5480d0a80904141502y5b551654t1c38a9127305ba53@mail.gmail.com> (mario guerra's message of "Tue\, 14 Apr 2009 17\:02\:03 -0500")
mario guerra <emailformario@gmail.com> writes:
> I work for a chip company that produces a C++ simulator for one of our
> processor cores, which we deliver as a shared object file. We've used
> GCC version 3.3.3 to build it, since that is the standard version
> deployed within our company. However, some of our customers are
> attempting to incorporate our model into third party simulation
> environments which use different versions of GCC, and this sometimes
> causes segmentation faults at run time from calls into the stdc++
> library. We're trying to find a way to support customers who may be
> using different versions of GCC without having to create a custom
> simulator build for each customer.
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.
Ian
next prev parent reply other threads:[~2009-04-14 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2009-04-15 15:09 ` John Fine
2009-04-16 17:06 ` Andrew Haley
2009-04-15 17:09 mario guerra
2009-04-15 17:13 mario guerra
2009-04-15 17:40 ` Ian Lance Taylor
2009-04-17 14:55 mario guerra
2009-04-17 15:30 ` Ian Lance Taylor
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=m3ws9m27wu.fsf@google.com \
--to=iant@google.com \
--cc=emailformario@gmail.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).