This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: egcs-980315, gen*.c system.h and fatal() using stdarg/varargs

 > From: Jeffrey A Law <>
 >   In message <>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
 > something.
 > My only real concern about linking in libiberty to gcc is that
 > libiberty isn't autoconf'd.
 > jeff

	Getting gcc to cleanly link with libiberty and ironing out all
the related issues is IMHO a non-trivial task.  It would require someone
taking ownership to see it through.  When this last came up, I don't
think there were any takers.  I could be mis-remembering the
conversation though...  Best check the archive. 

Kaveh R. Ghazi			Project Manager / Custom Development		Icon CMT Corp.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]