This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Libiberty's snprintf for v3?
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- To: schwab at suse dot de
- Cc: dj at redhat dot com, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org, pcarlini at unitus dot it
- Date: Tue, 22 Apr 2003 19:14:51 -0400 (EDT)
- Subject: Re: Libiberty's snprintf for v3?
- References: <3EA44576.90708@unitus.it> <200304220041.UAA22116@caip.rutgers.edu> <jewuhm52lq.fsf@sykes.suse.de>
> From: Andreas Schwab <schwab at suse dot de>
>
> "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu> writes:
>
> |> C. I'm not sure if it's legal (portable) to traverse the va_list
> |> twice inside vsnprintf.c, once with vfprintf and once is vsprintf.
>
> It is only legal when both traverses are either bracketed by
> va_start/va_end, or you use va_copy to copy the va_alist object. va_copy
> is a C99 feature, if it isn't provided use __va_copy if defined, else a
> simple assignment.
> Andreas.
Thanks, I've snarfed the va_copy defaults from gcc/system.h.
--
Kaveh R. Ghazi ghazi at caip dot rutgers dot edu