public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/65812] gcc 4.9.1 doesn't warn about uninitialized variable use declared in a switch/case statement when compiled with -O Date: Mon, 20 Apr 2015 10:46:00 -0000 [thread overview] Message-ID: <bug-65812-4-wTFlVNhQ9I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65812-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65812 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-04-20 Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- This is because at the point where we warn we don't know that the code is executed unconditionally and with optimization we don't warn about maybe-uninitialized uses early. Late we have removed all code as dead and thus do not warn either. I'd say it works as intended (even though surprising).
next prev parent reply other threads:[~2015-04-20 10:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-20 10:37 [Bug c/65812] New: " joe at perches dot com 2015-04-20 10:46 ` rguenth at gcc dot gnu.org [this message] 2015-04-20 11:18 ` [Bug c/65812] " joe at perches dot com 2015-04-20 13:42 ` mpolacek at gcc dot gnu.org 2015-04-20 13:43 ` jakub at gcc dot gnu.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-65812-4-wTFlVNhQ9I@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).