public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Wolfgang at Solfrank dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/50581] stdarg doesn't support array types
Date: Sat, 01 Oct 2011 14:43:00 -0000	[thread overview]
Message-ID: <bug-50581-4-eCNgogi9u7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50581-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50581

--- Comment #4 from Wolfgang at Solfrank dot net 2011-10-01 14:43:32 UTC ---
(In reply to comment #3)

Thanks for the insight regarding passing arrays by value in C90, I wasn't even
aware of that.

However:

> Passing va_list as a function argument is generally hard, whether or not 
> variadic, since you don't know whether it will be passed by reference or 
> by value or what the type of the address of a va_list parameter will be.  
> Portable code needs to pass a pointer to va_list or a structure containing 
> va_list or use some other such means of avoiding dependence on whether 
> va_list is an array.

Huh?  What about vprintf and friends?  They are defined to take a va_list as
their last parameter.


  parent reply	other threads:[~2011-10-01 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 15:49 [Bug c/50581] New: " Wolfgang at Solfrank dot net
2011-09-30 20:13 ` [Bug c/50581] " joseph at codesourcery dot com
2011-10-01 11:07 ` Wolfgang at Solfrank dot net
2011-10-01 14:08 ` joseph at codesourcery dot com
2011-10-01 14:43 ` Wolfgang at Solfrank dot net [this message]
2011-10-01 18:46 ` joseph at codesourcery dot com
2011-10-02 16:09 ` Wolfgang at Solfrank dot net
2011-10-02 19:48 ` svfuerst at gmail dot com
2022-01-03  2:38 ` pinskia at gcc dot gnu.org

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=bug-50581-4-eCNgogi9u7@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).