public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/36168] Incorrect (and strange) warnings with -Wuninitialized Date: Wed, 07 May 2008 09:44:00 -0000 [thread overview] Message-ID: <20080507094319.28329.qmail@sourceware.org> (raw) In-Reply-To: <bug-36168-2736@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pinskia at gcc dot gnu dot org 2008-05-07 09:43 ------- This is a normal issue with the unitialized warnings. See PR 5035. Basically to get this warning correct for this case, you need conditional PHIs which we don't have currently. And I don't know of any compiler that does. Basically the code looks like: if (a) set b for(...) for(...) if (a) use b Unswitching the loops will help somewhat as then you can then jump thread. Thanks, Andrew Pinski -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |24639 nThis| | Severity|normal |enhancement Keywords|diagnostic | Known to fail|4.2.3 4.4.0 | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36168
next prev parent reply other threads:[~2008-05-07 9:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-07 9:34 [Bug c++/36168] New: " martin at mpa-garching dot mpg dot de 2008-05-07 9:35 ` [Bug c++/36168] " martin at mpa-garching dot mpg dot de 2008-05-07 9:44 ` pinskia at gcc dot gnu dot org [this message] 2008-05-07 9:51 ` pinskia at gcc dot gnu dot org 2008-05-07 9:52 ` martin at mpa-garching dot mpg dot de 2008-05-07 9:54 ` pinskia at gcc dot gnu dot org 2008-05-07 9:57 ` martin at mpa-garching dot mpg dot de 2008-05-07 10:13 ` manu at gcc dot gnu dot org 2008-08-29 3:53 ` manu at gcc dot gnu dot org 2008-12-28 5:13 ` pinskia at gcc dot gnu dot org 2009-02-09 16:13 ` [Bug c++/36168] bogus uninitialized warning (huge testcase) manu at gcc dot gnu dot org 2009-02-09 16:15 ` manu 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=20080507094319.28329.qmail@sourceware.org \ --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).