This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH RFC: Remove fork from collect2
- From: Dale Johannesen <dalej at apple dot com>
- To: Ian Lance Taylor <ian at wasabisystems dot com>
- Cc: Andrew Pinski <apinski at apple dot com>, "gcc at gcc dot gnu dot org list" <gcc at gcc dot gnu dot org>, Dale Johannesen <dalej at apple dot com>, Caroline Tice <ctice at apple dot com>
- Date: Fri, 19 Mar 2004 14:52:11 -0800
- Subject: Re: PATCH RFC: Remove fork from collect2
- References: <20040317023814.10143.qmail@gossamer.airs.com> <20040317092131.GA95030@lorien.int.gecko.de> <m3smg7r5cw.fsf@gossamer.airs.com> <20040317133116.GA15850@lorien.int.gecko.de> <m3k71jr29k.fsf@gossamer.airs.com> <20040317170336.GA16667@lorien.int.gecko.de> <87d67bw7bd.fsf@egil.codesourcery.com> <m3vfl3kyfr.fsf@gossamer.airs.com> <A7570576-79EC-11D8-9F81-000393BB90B6@apple.com> <009F425B-79EE-11D8-92E2-00039372607E@apple.com> <m38yhw4gai.fsf@gossamer.airs.com>
On Mar 19, 2004, at 2:34 PM, Ian Lance Taylor wrote:
Is there some command line
option we could use to disable that, to generate code which could be
linked by either Apple gcc or FSF gcc? Note in particular that there
is no floating point code between the vfork and the exec, so there is
no actual need to save the floating point state.
No. I thought there was a switch to generate FP save/restore inline,
but there isn't.
Also note that
generating calls to functions which are in the user's namespace would
appear to be a bad thing.
They are not in the user's namespace; external names have a prepended
underscore on Darwin, these names do not.
3) Add restFP and saveFP to FSF gcc. Overall consistency would appear
to be a good thing.
It would. (These routines predate anybody now working at Apple, and
don't "belong" to anybody.)
However, as I said, I don't think that's a general solution to the
problem.
Indeed, any solution that makes use of the fact that Apple's system
compiler happens to be gcc is not the right approach IMO.
What's wrong with building libiberty on each pass through the bootstrap?
That would solve the general problem, and that library builds very
quickly.