Exceptions workaround for older systems that don't USE_COLLECT2

Jamie Lokier egcs@tantalophile.demon.co.uk
Sun Sep 6 17:36:00 GMT 1998


On Sun, Sep 06, 1998 at 02:11:11AM -0700, Melissa O'Neill wrote:
> That's certainly a possible solution and likely the best compromise.
> The downside is that collect2 would do static constructor/destructor
> handling when NeXT's ld is happy to handle it.  And, since many C++
> programs don't use exceptions at all, the overhead of always using
> collect2's double-link strategy for those common cases seems a little
> burdensome.

If collect2 doesn't find anything it needs to handle itself (i.e.,
exceptions in this case), can it skip the second link and just use the
output of the first?

-- Jamie



More information about the Gcc mailing list