This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Bug: Missing va_end() in cygwin_internal()

> -----Original Message-----
> From: cygwin-owner On Behalf Of Max Bowsher
> Sent: 30 December 2004 19:05

> Christopher Faylor wrote:
> > On Thu, Dec 30, 2004 at 05:59:02PM -0000, Max Bowsher wrote:
> >> There is no va_end() call in cygwin_internal().
> >
> > Or in functions from:
> >
> >
> >
> >
> >
> >
> > The lack doesn't seem to be causing much of a problem...
> Standards say va_end is required, but may be a noop in some 
> implementations.

  99.9% of all known implementations.  I guess it might be an issue if one day
we want to port cygwin to run on Vax or somesuch....

> I peered at the guts of gcc trying to work out whether that 
> was the case for cygwin, but got too lost to be sure.

  AFAICS gcc supplies the mechanics to implement va_start and va_arg however
your architecture requires, but no way to define any functionality for va_end at

  Ah, found it.  EXPAND_BUILTIN_VA_END was removed by 

I guess that VAX port will be ok after all, since it's being a supported
architecture for gcc means that it must not need va_end....

Can't think of a witty .sigline today....

Unsubscribe info:
Problem reports:

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