From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Andreas Schwab <schwab@linux-m68k.org>,
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] wchar: Define va_list for POSIX (BZ #30035)
Date: Thu, 25 May 2023 13:43:16 -0300 [thread overview]
Message-ID: <be71cdbe-630a-e4f8-be2a-cad622dea9f7@linaro.org> (raw)
In-Reply-To: <mvm353ke92l.fsf@linux-m68k.org>
On 25/05/23 12:15, Andreas Schwab wrote:
> 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?
The conform tests seems to not require it, but I don't see why not.
prev parent reply other threads:[~2023-05-25 16:43 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
2023-05-25 16:43 ` Adhemerval Zanella Netto [this message]
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=be71cdbe-630a-e4f8-be2a-cad622dea9f7@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).