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: Ian Lance Taylor <ian at wasabisystems dot com>
- To: Dale Johannesen <dalej at apple 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>, Caroline Tice <ctice at apple dot com>
- Date: 19 Mar 2004 17:56:03 -0500
- 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><2888B7BB-79F2-11D8-A952-000A95D7CD40@apple.com>
Dale Johannesen <dalej@apple.com> writes:
> This must have come up before; HP, for example, has a lot of magic
> library routines.
> What's the expected resolution? Just don't put things in libiberty
> that do that?
This is only a problem if the HP compiler causes the code to call
functions which are in libraries which gcc does not link against.
Perhaps there are no such functions, or perhaps libiberty simply
doesn't generate calls to them.
Ian