This is the mail archive of the
mailing list for the GCC project.
Re: egcs-980315, gen*.c system.h and fatal() using stdarg/varargs
- To: Robert Lipe <robertl at dgii dot com>
- Subject: Re: egcs-980315, gen*.c system.h and fatal() using stdarg/varargs
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 25 Mar 1998 10:58:03 -0700
- cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <firstname.lastname@example.org>you write:
> Kaveh R. Ghazi wrote:
> > This should allow us to use vfprintf with impunity, iff we
> > assume we can always fall back on varargs.h/va_arg().
> Isn't this the very sort of problem that libiberty was invented to solve?
> The program uses robust, standards-conforumant function and if the host
> system doesn't have them, libiberty gives them to you?
> I don't know if libiberty actually has the functionality needed here,
> but it seems like a good place to start looking.
Or maybe now is the time to enhance libiberty if it's missing
My only real concern about linking in libiberty to gcc is that
libiberty isn't autoconf'd.