On Wed, Dec 29, 2010 at 7:53 AM, Tim van der Molen wrote:
...
> It does indeed. In fact, some of the stdarg.h headers (e.g. powerpc)
> take this approach. Here is a diff for the remaining headers.
Looks good to me. I suspect sys/arch/m88k/include/va-m88k.h could use
some tweaking too, but it's d
On Wed, 29 Dec 2010 02:30:37 +0100, Ted Unangst wrote:
> On Tue, Dec 28, 2010 at 6:59 PM, Tim van der Molen wrote:
> > So, to conclude, what I would like to propose is the following:
> > * Hide from lint the va_copy() macro in .
> > * Add a lint-friendly va_copy() macro to
> > /usr/src/sys/arch/*
On Tue, Dec 28, 2010 at 6:59 PM, Tim van der Molen wrote:
> So, to conclude, what I would like to propose is the following:
> * Hide from lint the va_copy() macro in .
> * Add a lint-friendly va_copy() macro to
> /usr/src/sys/arch/*/include/stdarg.h.
Does adding a lint friendly __va_copy to arch
lint currently does not properly handle va_copy(): a statement like
"va_copy(ap2, ap);" causes lint to issue warnings like
test.c:14: warning: ap2 may be used before set
Lint pass2:
test.c:14: __va_copy used, but not defined
Defining the following macro would be sufficient to prevent these
warnin
