This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [libstdc++] Make use of runtime demangler
- From: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>,phil at jaj dot com
- Cc: aoliva at redhat dot com,davem at redhat dot com,gcc-patches at gcc dot gnu dot org,libstdc++ at gcc dot gnu dot org,mark at codesourcery dot com
- Date: Sat, 4 May 2002 17:48:43 +0200
- Subject: Re: [libstdc++] Make use of runtime demangler
- References: <20020329182924.A31493@disaster.basement.lan> <oradrgtsev.fsf@livre.redhat.lsd.ic.unicamp.br> <200205041419.KAA18643@caip.rutgers.edu>
On Saturday 04 May 2002 16:19, Kaveh R. Ghazi wrote:
> > From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
> >
> > Kaveh, do you really need the extra check for stdlib.h on your platform?
> > On Linux the stuff in acinclude handles that, so only a new check for
> > string.h is missing.
>
> No. I didn't really need stdlib.h, only string.h is explicitly
> necessary once the DEFS were set appropriately. However I found that
> libstdc++-v3's configure was very convoluted and felt better listing
> both with a comment explaining why they were necessary was more clear.
> At worst you'd pull it from cache for subsequent queries.
I wasn't sure whether the header checks in were doing something special for
cros builds etc., so I stayed out of this area for now :-).
> But I'm not married to my approach. If your patch works then I'll
> hold off checking in mine. If it fixes the implicit decls on linux,
> then I'm sure it'll do so on solaris and irix. There was nothing
> platform specific about my patch.
Fine with me too, lets wait for someone to decide which way to go :-).
Franz.