supporting multiple versions of GCC with a single shared object release?

[Ian Lance Taylor]

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