From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v3 4/7] Add __v*printf_internal with flags arguments
Date: Thu, 22 Nov 2018 17:59:00 -0000 [thread overview]
Message-ID: <5532dc50-c180-338a-edaf-4556771771f7@linaro.org> (raw)
In-Reply-To: <80aca9c1-0192-38d9-9f08-70c5765fa1f8@linaro.org>
On 22/11/2018 15:55, Adhemerval Zanella wrote:
>
>
> On 15/11/2018 19:44, Gabriel F. T. Gomes wrote:
>> From: Zack Weinberg <zackw@panix.com>
>>
>> Changes since v2:
>>
>> - Expanded the comments about PRINTF_LDBL_IS_DBL and PRINTF_FORTIFY.
>> - Removed the parameter-less macros LDBL_IS_DBL and DO_FORTIFY.
>> Explicitly compare the flags.
>
> LGTM, thanks.
And, as before please add a note on CL that it fixes BZ#11319 by unifying both
fortified and non-fortified vdprintf initialization.
next prev parent reply other threads:[~2018-11-22 17:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 21:45 [PATCH v3 0/7] Use more flags parameters instead of global bits in stdio Gabriel F. T. Gomes
2018-11-15 21:46 ` [PATCH v3 5/7] Add __vsyslog_internal, with same flags as __v*printf_internal Gabriel F. T. Gomes
2018-11-22 18:00 ` Adhemerval Zanella
2018-11-15 21:46 ` [PATCH v3 2/7] Use SCANF_ISOC99_A instead of _IO_FLAGS2_SCANF_STD Gabriel F. T. Gomes
2018-11-22 17:38 ` Adhemerval Zanella
2018-11-15 21:46 ` [PATCH v3 3/7] Use SCANF_LDBL_IS_DBL instead of __ldbl_is_dbl Gabriel F. T. Gomes
2018-11-22 17:39 ` Adhemerval Zanella
2018-11-15 21:46 ` [PATCH v3 1/7] Add __vfscanf_internal and __vfwscanf_internal with flags arguments Gabriel F. T. Gomes
2018-11-16 18:34 ` Gabriel F. T. Gomes
2018-11-22 17:35 ` Adhemerval Zanella
2018-12-04 15:15 ` Gabriel F. T. Gomes
2018-12-04 17:37 ` Adhemerval Zanella
2018-11-15 21:46 ` [PATCH v3 6/7] Use PRINTF_FORTIFY instead of _IO_FLAGS2_FORTIFY (bug 11319) Gabriel F. T. Gomes
2018-11-22 18:11 ` Adhemerval Zanella
2018-12-04 16:20 ` Gabriel F. T. Gomes
2018-12-04 17:40 ` Adhemerval Zanella
2018-12-04 18:01 ` Gabriel F. T. Gomes
2018-12-04 21:07 ` Adhemerval Zanella
2018-12-05 16:53 ` Gabriel F. T. Gomes
2018-12-05 18:14 ` Adhemerval Zanella
2018-12-05 19:12 ` Gabriel F. T. Gomes
2018-12-05 19:18 ` Adhemerval Zanella
2018-12-05 19:27 ` Gabriel F. T. Gomes
2018-12-05 19:35 ` Adhemerval Zanella
2018-12-05 20:07 ` Gabriel F. T. Gomes
2018-12-18 13:03 ` Szabolcs Nagy
2018-12-18 16:54 ` Florian Weimer
2018-12-18 17:32 ` Gabriel F. T. Gomes
2018-12-19 15:31 ` Szabolcs Nagy
2018-12-20 22:17 ` Gabriel F. T. Gomes
2018-11-15 21:46 ` [PATCH v3 4/7] Add __v*printf_internal with flags arguments Gabriel F. T. Gomes
2018-11-22 17:46 ` Adhemerval Zanella
2018-11-22 17:55 ` Adhemerval Zanella
2018-11-22 17:59 ` Adhemerval Zanella [this message]
2018-11-15 21:53 ` [PATCH v3 7/7] Use PRINTF_LDBL_IS_DBL instead of __ldbl_is_dbl Gabriel F. T. Gomes
2018-11-22 18:13 ` Adhemerval Zanella
2018-12-02 11:53 ` [PATCH v3 0/7] Use more flags parameters instead of global bits in stdio Florian Weimer
2018-12-03 13:52 ` Gabriel F. T. Gomes
2018-12-05 21:00 ` Gabriel F. T. Gomes
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=5532dc50-c180-338a-edaf-4556771771f7@linaro.org \
--to=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).