From: bugzilla-daemon@bugzilla.kernel.org
To: linux-sparse@vger.kernel.org
Subject: [Bug 207959] Don't warn about the universal zero initializer for a structure with the 'designated_init' attribute.
Date: Thu, 28 May 2020 19:22:14 +0000 [thread overview]
Message-ID: <bug-207959-200559-IG36fkwdeW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207959-200559@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207959
Luc Van Oostenryck (luc.vanoostenryck@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luc.vanoostenryck@gmail.com
--- Comment #1 from Luc Van Oostenryck (luc.vanoostenryck@gmail.com) ---
In fact, sparse already support this via the option
'-Wno-universal-initializer'. It's really very recent and thus only in the
mainline tree, not in a release (and it was introduced for another warning but
the result is the same).
My very personal point of view is that the correct syntax should be '{ }'
because it conveys much better the idea of a default initializer. This single
zero in '{ 0 }' is just confusing.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-05-28 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 16:27 [Bug 207959] New: Don't warn about the universal zero initializer for a structure with the 'designated_init' attribute bugzilla-daemon
2020-05-28 19:22 ` bugzilla-daemon [this message]
2020-05-28 19:57 ` Ramsay Jones
2020-05-28 20:52 ` [Bug 207959] " bugzilla-daemon
2020-05-28 21:24 ` bugzilla-daemon
2020-05-28 22:25 ` Linus Torvalds
2020-05-28 22:26 ` bugzilla-daemon
2020-05-28 22:31 ` bugzilla-daemon
2020-05-28 22:47 ` bugzilla-daemon
2020-05-29 19:35 ` bugzilla-daemon
2020-05-29 19:47 ` bugzilla-daemon
2020-06-08 7:53 ` bugzilla-daemon
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=bug-207959-200559-IG36fkwdeW@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-sparse@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.