public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "maierkom at rcs dot ei dot tum dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/18739] New: warning of uninitialized value gets suppressed without optimization with initialization after continue in loop
Date: Tue, 30 Nov 2004 14:06:00 -0000	[thread overview]
Message-ID: <20041130140535.18739.maierkom@rcs.ei.tum.de> (raw)

when compiling the following code without optimization no warning is given. when
optimization is enabled the following warning is printed:
warning: `i' might be used uninitialized in this function

This occures with gcc >= 3.3.2 (tested on 3.4.2 and 3.3.2) and independent of
host/target/build triplet (testet sparc-sun-solaris2.9 and i686-pc-linux-gnu)
with c and c++ frontend.

int a();

int b();

void f(int j)
{
	int i;
	do {
		if (a())
			continue;
		i = b();
	} while (i);
}

-- 
           Summary: warning of uninitialized value gets suppressed without
                    optimization with initialization after continue in loop
           Product: gcc
           Version: 3.4.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: maierkom at rcs dot ei dot tum dot de
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: sparc-sun-solaris2.9
  GCC host triplet: sparc-sun-solaris2.9
GCC target triplet: sparc-sun-solaris2.9


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


             reply	other threads:[~2004-11-30 14:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 14:06 maierkom at rcs dot ei dot tum dot de [this message]
2004-11-30 14:17 ` [Bug c/18739] " pinskia 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=20041130140535.18739.maierkom@rcs.ei.tum.de \
    --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).