From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Ser, Simon" <simon.ser@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] meson: add -Wno-missing-braces
Date: Wed, 20 Mar 2019 15:52:04 +0200 [thread overview]
Message-ID: <20190320135204.GJ3888@intel.com> (raw)
In-Reply-To: <0fa8cad45c9fa58e39518aaf1364fc916b4782d5.camel@intel.com>
On Wed, Mar 20, 2019 at 10:53:05AM +0000, Ser, Simon wrote:
> On Wed, 2019-03-20 at 11:38 +0200, Jani Nikula wrote:
> > On Wed, 20 Mar 2019, "Ser, Simon" <simon.ser@intel.com> wrote:
> > > Enabling -Werror=missing-braces results in this error with Clang:
> > >
> > > ../tests/kms_vrr.c:203:20: error: suggest braces around
> > > initialization of subobject [-Werror,-Wmissing-braces]
> > > drmVBlank vbl = { 0 };
> > > ^
> > > {}
> > >
> > > I don't believe there is any value in keeping this, so let's just
> > > disable it.
> >
> > I fail to come up with examples right now, but I think there are
> > legitimate cases for the warning.
> >
> > Arguably the above initializer should be written as simply {} instead
> > of
> > having the 0 value for initializing the first member which happens to
> > be
> > a substruct.
>
> Unfortunately using {} is a GNU extension, and ISO C forbids empty
> initializer lists.
>
> Does IGT use un-standardized extensions?
$ git grep '=[ ]*{[ ]*}' | wc -l
195
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-03-20 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 8:52 [igt-dev] [PATCH i-g-t] meson: add -Wno-missing-braces Ser, Simon
2019-03-20 9:38 ` Jani Nikula
2019-03-20 10:53 ` Ser, Simon
2019-03-20 12:11 ` Jani Nikula
2019-03-20 12:22 ` Petri Latvala
2019-03-21 7:25 ` Ser, Simon
2019-03-21 7:21 ` Ser, Simon
2019-03-20 13:52 ` Ville Syrjälä [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=20190320135204.GJ3888@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=simon.ser@intel.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