From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 1/2] capability: Introduce capability API
Date: Fri, 30 Aug 2019 16:48:10 +0200 [thread overview]
Message-ID: <20190830144810.GA25654@rei> (raw)
In-Reply-To: <20190829210810.GC5711@dell5510>
Hi!
> There is a warning, but I guess that's just gcc being paranoid:
> test_guarded_buf.c:93:1: warning: missing initializer for field ???caps??? of ???struct tst_test??? [-Wmissing-field-initializers]
> 93 | };
> | ^
> In file included from test_guarded_buf.c:12:
> ../../include/tst_test.h:214:18: note: ???caps??? declared here
> 214 | struct tst_cap *caps;
> | ^~~~
That sounds like a gcc bug since for designated initializers omitted
fields are implicitly initialized to zero, there is no point in
producing warnings like this one. I guess that we trigger that by
inlining a structure that is inialized by mixing plain and designated
initalizers in the middle of the structure.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-08-30 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 9:46 [LTP] [PATCH v3 1/2] capability: Introduce capability API Richard Palethorpe
2019-08-23 9:46 ` [LTP] [PATCH v3 2/2] capability: library tests Richard Palethorpe
2019-08-29 21:18 ` Petr Vorel
2019-08-28 10:43 ` [LTP] [PATCH v3 1/2] capability: Introduce capability API Li Wang
2019-08-28 11:58 ` Richard Palethorpe
2019-08-29 21:08 ` Petr Vorel
2019-08-30 14:48 ` Cyril Hrubis [this message]
2019-09-04 12:11 ` [LTP] [PATCH v4 " Richard Palethorpe
2019-09-04 12:11 ` [LTP] [PATCH v4 2/2] capability: library tests Richard Palethorpe
2019-09-11 14:41 ` [LTP] [PATCH v4 1/2] capability: Introduce capability API Cyril Hrubis
2019-09-11 15:10 ` Richard Palethorpe
2019-09-11 15:33 ` Cyril Hrubis
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=20190830144810.GA25654@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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