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 middle-end/50040] [4.5/4.6/4.7 Regression] missed warning: ‘x.y’ is used uninitialized in this function Date: Thu, 11 Aug 2011 14:29:00 -0000 [thread overview] Message-ID: <bug-50040-4-ssGvKwakWc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50040-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50040 --- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-08-11 14:28:39 UTC --- Author: rguenth Date: Thu Aug 11 14:28:36 2011 New Revision: 177667 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=177667 Log: 2011-08-11 Richard Guenther <rguenther@suse.de> PR middle-end/50040 * gimplify.c (gimplify_modify_expr_complex_part): Mark the load of the other piece with TREE_NO_WARNING. * tree-flow.h (warn_uninit): Adjust prototype. * tree-ssa.c (warn_uninit): Take uninitialized SSA name, the base variable and the expression that is used separately. Properly query all TREE_NO_WARNING flags. (struct walk_data): Remove. (warn_uninitialized_var): Likewise. (warn_uninitialized_vars): Do not walk gimple pieces but simply look at all SSA uses of the statement. Handle unused memory separately. * tree-ssa-uninit.c (warn_uninitialized_phi): Adjust. * g++.dg/warn/unit-1.C: Un-XFAIL. * gcc.dg/uninit-I.c: Likewise. Modified: trunk/gcc/ChangeLog trunk/gcc/gimplify.c trunk/gcc/testsuite/g++.dg/warn/unit-1.C trunk/gcc/testsuite/gcc.dg/uninit-I.c trunk/gcc/tree-flow.h trunk/gcc/tree-ssa-uninit.c trunk/gcc/tree-ssa.c
next prev parent reply other threads:[~2011-08-11 14:29 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-10 19:29 [Bug middle-end/50040] New: " jan.kratochvil at redhat dot com 2011-08-11 10:04 ` [Bug middle-end/50040] " rguenth at gcc dot gnu.org 2011-08-11 10:42 ` jan.kratochvil at redhat dot com 2011-08-11 10:58 ` rguenth at gcc dot gnu.org 2011-08-11 11:23 ` jan.kratochvil at redhat dot com 2011-08-11 14:29 ` rguenth at gcc dot gnu.org [this message] 2011-08-11 14:30 ` [Bug middle-end/50040] [4.5/4.6 " rguenth at gcc dot gnu.org 2011-11-02 9:51 ` rguenth at gcc dot gnu.org 2011-11-03 15:15 ` rguenth at gcc dot gnu.org 2012-01-03 13:31 ` rguenth at gcc dot gnu.org 2012-01-03 13:32 ` rguenth at gcc dot gnu.org 2012-01-03 15:17 ` rguenth at gcc dot gnu.org 2012-01-03 16:55 ` sezeroz at gmail dot com 2012-06-20 13:03 ` rguenth at gcc dot gnu.org 2012-07-02 11:40 ` rguenth at gcc dot gnu.org 2013-04-12 16:18 ` [Bug middle-end/50040] [4.6 " 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-50040-4-ssGvKwakWc@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).