public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mimomorin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58711] New: Missing "uninitialized" warning in loop condition (when compiling without optimization)
Date: Sun, 13 Oct 2013 05:10:00 -0000	[thread overview]
Message-ID: <bug-58711-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58711

            Bug ID: 58711
           Summary: Missing "uninitialized" warning in loop condition
                    (when compiling without optimization)
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mimomorin at gmail dot com

In the following code, `cond` is uninitialized in `while (cond)`. However, 
the "uninitialized" warning (i.e. "variable 'cond' is uninitialized when used
here") 
does not emit when compiling without optimization.
(If we compile it with optimization option, the warning is properly emitted.)
Tested on gcc 4.4-4.8, 4.9 (trunk).

int main(int argc, char* argv[])
{
    int cond;

    // Missing "uninitialized" warning
    while (cond != 0) {
        // `(void)` is used to avoid "unused-value" warning
        (void)&cond;
    }

    return 0;
}

Clang has the same issue, but it's fixed recently.
( http://llvm.org/bugs/show_bug.cgi?id=16054 )


                 reply	other threads:[~2013-10-13  5:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-58711-4@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).