public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "safinaskar at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53119] -Wmissing-braces wrongly warns about universal zero initializer {0}
Date: Sat, 07 Feb 2015 00:24:00 -0000	[thread overview]
Message-ID: <bug-53119-4-ImmJn5imdS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53119-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119

Askar Safin <safinaskar at mail dot ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |safinaskar at mail dot ru

--- Comment #21 from Askar Safin <safinaskar at mail dot ru> ---
Same bug in clang: http://llvm.org/bugs/show_bug.cgi?id=21689
Related bug in POSIX: http://austingroupbugs.net/view.php?id=918

And I think this bug should be fixed even in C++, just because we should have
some uniform way to initialize addrinfo and mbstate_t in both C and C++ :)
(And gcc 4.9.2 emits warning for C++ but not for C)


  parent reply	other threads:[~2015-02-07  0:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 17:04 [Bug c/53119] New: -Wbraces " bugdal at aerifal dot cx
2012-04-25 17:53 ` [Bug c/53119] " manu at gcc dot gnu.org
2012-04-25 18:02 ` [Bug c/53119] -Wmissing-braces " bugdal at aerifal dot cx
2012-04-25 18:13 ` manu at gcc dot gnu.org
2012-04-25 18:32 ` bugdal at aerifal dot cx
2012-04-25 22:13 ` manu at gcc dot gnu.org
2012-04-26 10:37 ` joseph at codesourcery dot com
2012-04-26 10:46 ` manu at gcc dot gnu.org
2012-04-26 10:51 ` joseph at codesourcery dot com
2012-05-03 17:55 ` manu at gcc dot gnu.org
2013-08-14 11:36 ` jnahughes at googlemail dot com
2013-09-07 18:15 ` manu at gcc dot gnu.org
2014-06-05 19:36 ` law at gcc dot gnu.org
2014-06-06  0:57 ` bugdal at aerifal dot cx
2014-06-06  5:01 ` mpolacek at gcc dot gnu.org
2014-08-03 17:40 ` rose.garcia-eggl2fk at yopmail dot com
2014-08-03 17:58 ` mpolacek at gcc dot gnu.org
2014-08-03 19:33 ` rose.garcia-eggl2fk at yopmail dot com
2015-01-21 18:57 ` rogerdpack at gmail dot com
2015-01-21 19:29 ` mpolacek at gcc dot gnu.org
2015-02-07  0:24 ` safinaskar at mail dot ru [this message]
2015-02-07  0:31 ` bugdal at aerifal dot cx
2015-02-07  1:02 ` safinaskar at mail dot ru
2015-03-16  4:32 ` nightstrike at gmail dot com

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-53119-4-ImmJn5imdS@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).