This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Exceptions workaround for older systems that don't USE_COLLECT2
- To: "Melissa O'Neill" <oneill at cs dot sfu dot ca>, law at cygnus dot com
- Subject: Re: Exceptions workaround for older systems that don't USE_COLLECT2
- From: Jamie Lokier <egcs at tantalophile dot demon dot co dot uk>
- Date: Sun, 6 Sep 1998 19:24:17 +0100
- Cc: egcs at cygnus dot com
- References: <24907.905069305@hurl.cygnus.com> <199809060911.CAA11830@daisy.css.sfu.ca>
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