From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] u9fs and va_copy()
Date: Thu, 16 Sep 2004 10:49:27 -0400 [thread overview]
Message-ID: <b44864ca97531a92bcddd4d2083c278e@plan9.bell-labs.com> (raw)
Eric Van Hensbergen <ericvh@gmail.com> has provided a fix for u9fs on the PowerPC.
The va_copy() macro is needed if the type of va_list is not an array (as it is on all
the current Plan 9 compilers I believe).
There may be other software ported between Plan 9 and other systems which could run
foul of the va_copy() macro. Should we add it to the Plan9 header files and check
all our code conforms to the correct use of variable arguments as specified in C99?
--jim
next reply other threads:[~2004-09-16 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 14:49 jmk [this message]
2004-09-16 15:24 ` Rob Pike
2004-09-20 9:02 Aharon Robbins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b44864ca97531a92bcddd4d2083c278e@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).