public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/34772] [4.3/4.4/4.5/4.6 Regression] self-initialisation does not silence uninitialised warnings (-Winit-self ignored) Date: Mon, 09 May 2011 21:04:00 -0000 [thread overview] Message-ID: <bug-34772-4-frtqMbL6Om@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-34772-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34772 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org Known to work| |4.7.0 Summary|[4.3/4.4/4.5/4.6/4.7 |[4.3/4.4/4.5/4.6 |Regression] |Regression] |self-initialisation does |self-initialisation does |not silence uninitialised |not silence uninitialised |warnings (-Winit-self |warnings (-Winit-self |ignored) |ignored) Known to fail| | --- Comment #17 from Jason Merrill <jason at gcc dot gnu.org> 2011-05-09 20:48:47 UTC --- Fixed on trunk so far.
next prev parent reply other threads:[~2011-05-09 21:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-34772-4@http.gcc.gnu.org/bugzilla/> 2011-05-09 17:49 ` [Bug c++/34772] [4.3/4.4/4.5/4.6/4.7 " jason at gcc dot gnu.org 2011-05-09 21:04 ` jason at gcc dot gnu.org [this message] 2011-06-27 13:07 ` [Bug c++/34772] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu.org 2011-06-27 16:43 ` [Bug c++/34772] [4.4/4.5/4.6 " manu at gcc dot gnu.org 2011-06-27 16:58 ` davi.arnaut at oracle dot com 2011-06-27 18:02 ` manu at gcc dot gnu.org 2011-06-27 19:17 ` davi.arnaut at oracle dot com 2008-01-13 18:24 [Bug c++/34772] New: -Winit-self ignored when compiling C++ (and ObjC++) olly at survex dot com 2010-05-22 18:21 ` [Bug c++/34772] [4.3/4.4/4.5/4.6 Regression] self-initialisation does not silence uninitialised warnings (-Winit-self ignored) rguenth at gcc dot gnu dot org
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-34772-4-frtqMbL6Om@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: linkBe 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).