public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH v2] wchar: Define va_list for POSIX (BZ #30035)
Date: Thu, 25 May 2023 17:15:30 +0200	[thread overview]
Message-ID: <mvm353ke92l.fsf@linux-m68k.org> (raw)
In-Reply-To: <20230124174959.1718640-1-adhemerval.zanella@linaro.org> (Adhemerval Zanella via Libc-alpha's message of "Tue, 24 Jan 2023 14:49:59 -0300")

On Jan 24 2023, Adhemerval Zanella via Libc-alpha wrote:

> diff --git a/conform/data/wchar.h-data b/conform/data/wchar.h-data
> index e414651a33..0af74e14bc 100644
> --- a/conform/data/wchar.h-data
> +++ b/conform/data/wchar.h-data
> @@ -15,6 +15,9 @@ type size_t
>  type locale_t
>  # endif
>  tag {struct tm}
> +# if !defined ISO99 && !defined ISO11 && !defined UNIX98
> +type va_list
> +# endif

Should this use the same construct wrt. va_list vs. __gnuc_va_list as in
stdio.h-data?

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  parent reply	other threads:[~2023-05-25 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 17:49 Adhemerval Zanella
2023-02-09 19:43 ` Adhemerval Zanella Netto
2023-03-22 13:11   ` Adhemerval Zanella Netto
2023-05-25 14:30     ` Adhemerval Zanella Netto
2023-05-25 15:15 ` Andreas Schwab [this message]
2023-05-25 16:43   ` Adhemerval Zanella Netto

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=mvm353ke92l.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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).