From: Paolo Bonzini <pbonzini@redhat.com>
To: Bill Wendling <morbo@google.com>, kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH] lib: use an argument which doesn't require default argument promotion
Date: Wed, 9 Oct 2019 12:13:24 +0200 [thread overview]
Message-ID: <eaec7e5d-af18-7818-b6d8-871674a4348a@redhat.com> (raw)
In-Reply-To: <CAGG=3QUL_OrjaWn+gF4z-R8brR2=3661hGk0uUAK2y8Dff7Mvg@mail.gmail.com>
On 10/09/19 01:11, Bill Wendling wrote:
> Clang warns that passing an object that undergoes default argument
> promotion to "va_start" is undefined behavior:
>
> lib/report.c:106:15: error: passing an object that undergoes default
> argument promotion to 'va_start' has undefined behavior
> [-Werror,-Wvarargs]
> va_start(va, pass);
>
> Using an "unsigned" type removes the need for argument promotion.
>
> Signed-off-by: Bill Wendling <morbo@google.com>
> ---
> lib/libcflat.h | 4 ++--
> lib/report.c | 6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/lib/libcflat.h b/lib/libcflat.h
> index b94d0ac..b6635d9 100644
> --- a/lib/libcflat.h
> +++ b/lib/libcflat.h
> @@ -99,9 +99,9 @@ void report_prefix_pushf(const char *prefix_fmt, ...)
> __attribute__((format(printf, 1, 2)));
> extern void report_prefix_push(const char *prefix);
> extern void report_prefix_pop(void);
> -extern void report(const char *msg_fmt, bool pass, ...)
> +extern void report(const char *msg_fmt, unsigned pass, ...)
> __attribute__((format(printf, 1, 3)));
> -extern void report_xfail(const char *msg_fmt, bool xfail, bool pass, ...)
> +extern void report_xfail(const char *msg_fmt, bool xfail, unsigned pass, ...)
> __attribute__((format(printf, 1, 4)));
> extern void report_abort(const char *msg_fmt, ...)
> __attribute__((format(printf, 1, 2)))
> diff --git a/lib/report.c b/lib/report.c
> index ca9b4fd..7d259f6 100644
> --- a/lib/report.c
> +++ b/lib/report.c
> @@ -81,7 +81,7 @@ void report_prefix_pop(void)
> }
>
> static void va_report(const char *msg_fmt,
> - bool pass, bool xfail, bool skip, va_list va)
> + unsigned pass, bool xfail, bool skip, va_list va)
> {
> const char *prefix = skip ? "SKIP"
> : xfail ? (pass ? "XPASS" : "XFAIL")
> @@ -104,7 +104,7 @@ static void va_report(const char *msg_fmt,
> spin_unlock(&lock);
> }
>
> -void report(const char *msg_fmt, bool pass, ...)
> +void report(const char *msg_fmt, unsigned pass, ...)
> {
> va_list va;
> va_start(va, pass);
> @@ -112,7 +112,7 @@ void report(const char *msg_fmt, bool pass, ...)
> va_end(va);
> }
>
> -void report_xfail(const char *msg_fmt, bool xfail, bool pass, ...)
> +void report_xfail(const char *msg_fmt, bool xfail, unsigned pass, ...)
> {
> va_list va;
> va_start(va, pass);
>
Applied, thanks.
Paolo
next prev parent reply other threads:[~2019-10-09 10:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 23:11 [kvm-unit-tests PATCH] lib: use an argument which doesn't require default argument promotion Bill Wendling
2019-09-10 16:43 ` Jim Mattson
2019-09-30 21:59 ` Bill Wendling
2019-10-09 10:13 ` Paolo Bonzini [this message]
2019-10-11 14:19 ` David Hildenbrand
2019-10-11 16:24 ` Thomas Huth
2019-10-11 16:36 ` Thomas Huth
2019-10-11 18:36 ` Bill Wendling
2019-10-14 7:57 ` Thomas Huth
2019-10-14 8:12 ` David Hildenbrand
2019-10-14 8:14 ` Bill Wendling
2019-10-14 9:32 ` Thomas Huth
2019-10-14 11:04 ` Paolo Bonzini
2019-10-17 12:32 ` Thomas Huth
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=eaec7e5d-af18-7818-b6d8-871674a4348a@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=morbo@google.com \
/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).