This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: supporting multiple versions of GCC with a single shared object release?
- From: Brian Budge <brian dot budge at gmail dot com>
- To: mario guerra <emailformario at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Tue, 14 Apr 2009 15:09:21 -0700
- Subject: Re: supporting multiple versions of GCC with a single shared object release?
- References: <5480d0a80904141452g45324a9ch68c1e1a6e5e51904@mail.gmail.com> <5480d0a80904141502y5b551654t1c38a9127305ba53@mail.gmail.com>
The only way I know of to do this reliably is to have a C interface.
The ABI breakages are definitely a bummer. The other option is to
have a build for each used ABI.
On Tue, Apr 14, 2009 at 3:02 PM, mario guerra <emailformario@gmail.com> wrote:
> Hello all,
>
> 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.
>
> Surely this problem has come up for others before. I'm looking for any
> suggestions as to how this problem might be solved, any ideas would be
> much appreciated.
>
> Thanks,
> Mario
>