This is the mail archive of the
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>
- Subject: Re: Exceptions workaround for older systems that don't USE_COLLECT2
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sat, 19 Sep 1998 23:33:41 -0600
- cc: Jason Merrill <jason at cygnus dot com>, egcs-patches at cygnus dot com, Jamie Lokier <egcs at tantalophile dot demon dot co dot uk>
- Reply-To: law at cygnus dot com
In message <199809192231.PAA25870@aldrington.ppp.cs.sfu.ca>you write:
> Jason Merrill writes:
> > I notice that the header talks about constructor_section(); if the target
> > supports named sections, you could use crtstuff instead of any linker
> > magic.
> Thanks to Jason for his observation. I've revised things so that the
> frame information is put in the __eh_frame section of the __TEXT segment.
> I've added the necessary code to crtstuff to handle the NEXTSTEP platform
> too. With these changes, exceptions work, and there's no need for
> collect2's double-link method.
> These patches assume the EGCS 1.1 source, where my earlier patch (which
> enabled collect2) has *not* been applied. The 19980914 snapshot has
> use_collect2=yes in configure for NEXTSTEP, which will cause the patch
> for configure to be rejected (but the other patches go through okay).
So, what do we do with x86-nextstep? Does it use mach-o? Are the
changes appropriate for that architecture too?