From: Peter Maydell <peter.maydell@linaro.org>
To: Eric Blake <eblake@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Kamil Rytarowski <kamil@netbsd.org>,
"patches@linaro.org" <patches@linaro.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH for-2.10] util/oslib-posix.c: Avoid warning on NetBSD
Date: Fri, 21 Jul 2017 11:22:59 +0100 [thread overview]
Message-ID: <CAFEAcA_mOeR2jTGuik6Jig972vMW5JTqQFaoZzt5_9oaG7D+aA@mail.gmail.com> (raw)
In-Reply-To: <eec67af4-3f8e-bb85-0854-61f4d450f627@redhat.com>
On 20 July 2017 at 19:26, Eric Blake <eblake@redhat.com> wrote:
> On 07/20/2017 11:32 AM, Peter Maydell wrote:
>> On NetBSD the compiler warns:
>> util/oslib-posix.c: In function 'sigaction_invoke':
>> util/oslib-posix.c:589:5: warning: missing braces around initializer [-Wmissing-braces]
>> siginfo_t si = { 0 };
>> ^
>
> Uggh. That is a broken compiler. C99 declares that 'anything = {0}' is
> supposed to be a valid way to zero-initialize anything.
>
>> util/oslib-posix.c:589:5: warning: (near initialization for 'si.si_pad') [-Wmissing-braces]
>>
>> because on this platform siginfo_t is defined as
>> typedef union siginfo {
>> char si_pad[128]; /* Total size; for future expansion */
>> struct _ksiginfo _info;
>> } siginfo_t;
>>
>> Avoid this warning by initializing the struct with {} instead;
>> this is a GCC extension but we use it all over the codebase already.
>
> Well, I'm glad that works to shut up the broken compiler.
>
>>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> ---
>> util/oslib-posix.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
Thanks; applied to master.
-- PMM
next prev parent reply other threads:[~2017-07-21 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 16:32 [Qemu-trivial] [PATCH for-2.10] util/oslib-posix.c: Avoid warning on NetBSD Peter Maydell
2017-07-20 18:26 ` [Qemu-trivial] [Qemu-devel] " Eric Blake
2017-07-20 20:53 ` Peter Maydell
2017-07-20 21:10 ` Eric Blake
2017-07-20 21:20 ` Peter Maydell
2017-07-21 10:22 ` Peter Maydell [this message]
2017-07-21 12:18 ` Kamil Rytarowski
2017-07-21 12:54 ` Eric Blake
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=CAFEAcA_mOeR2jTGuik6Jig972vMW5JTqQFaoZzt5_9oaG7D+aA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=eblake@redhat.com \
--cc=kamil@netbsd.org \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 NNTP newsgroup(s).