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 22:33:31 -0600
- cc: Jason Merrill <jason at cygnus dot com>, egcs 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 <199809190707.AAA02697@aldrington.ppp.cs.sfu.ca>you write:
> I think we can use named sections, and certainly if we can, we should
> to avoid the slowness of collect2. Enabling collect2 was Jeff Law's
> suggestion, and knowing little about the internals at the time, I accepted
> the fix (as time goes by, I seem to be learning more and more about how
> these things work, and so my viewpoint is getting clearer).
I thought enabling collect2 would be simpler and I don't really know
anything about Mach-O object formats.
If you think using crt* is better, that's fine with me. I'll table
your collect2 patch for now.
> If no one tells me why I shouldn't, I'll build a EGCS 1.1 variant that
> supports this strategy this weekend...
> P.S. I could do my changes for the current egcs snapshot, but I like to
> work on a base I know to be robust, so that I know any problems are mine.
When you actually submit the changes, it's better to submit them
against the mainline tree. Things change rapidly in this project, so
the egcs-1.1 code may not necessarily match the current egcs sources.