public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: thutt@vmware.com
To: gcc-gnats@gcc.gnu.org
Subject: c/5035: Incorrectly produces '`<var>' might be used uninitialized in this function'
Date: Thu, 06 Dec 2001 09:16:00 -0000	[thread overview]
Message-ID: <20011206170914.25904.qmail@sources.redhat.com> (raw)


>Number:         5035
>Category:       c
>Synopsis:       Incorrectly produces '`<var>' might be used uninitialized in this function'
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 06 09:16:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     thutt@vmware.com
>Release:        egcs-2.91.66
>Organization:
>Environment:
uname -a reports     : Linux thutt-lx 2.2.17 #3 Mon Oct 1 20:43:58 PDT 2001 i686 unknown
>Description:
gcc -v -c -O2 -Wall defect.c
Incorrectly produces the following warning:
 defect.c:7: warning: `b' might be used uninitialized in this function

'a' is local and not aliased.
'b' is local and not aliased.

Both uses of 'b' are under the same control conditions; the
compiler should not produce this warning.
>How-To-Repeat:
Follow instructions in source file.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="defect.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="defect.c"

LyoKICogZ2NjIC12IC1jIC1PMiAtV2FsbCBkZWZlY3QuYwogKgogKiBJbmNvcnJlY3RseSBwcm9k
dWNlcyB0aGUgZm9sbG93aW5nIHdhcm5pbmc6CiAqIAogKiAgZGVmZWN0LmM6Nzogd2FybmluZzog
YGInIG1pZ2h0IGJlIHVzZWQgdW5pbml0aWFsaXplZCBpbiB0aGlzIGZ1bmN0aW9uCiAqCiAqICAn
YScgaXMgbG9jYWwgYW5kIG5vdCBhbGlhc2VkLgogKiAgJ2InIGlzIGxvY2FsIGFuZCBub3QgYWxp
YXNlZC4KICoKICogIEJvdGggdXNlcyBvZiAnYicgYXJlIHVuZGVyIHRoZSBzYW1lIGNvbnRyb2wg
Y29uZGl0aW9uczsgdGhlCiAqICBjb21waWxlciBzaG91bGQgbm90IHByb2R1Y2UgdGhpcyB3YXJu
aW5nLgogKgogKiBnY2MgLS12ZXJzaW9uIHJlcG9ydHM6IGVnY3MtMi45MS42NgogKiB1bmFtZSAt
YSByZXBvcnRzICAgICA6IExpbnV4IHRodXR0LWx4IDIuMi4xNyAjMyBNb24gT2N0IDEgMjA6NDM6
NTggUERUIDIwMDEgaTY4NiB1bmtub3duCiAqIAogKi8KZXh0ZXJuIGludCBmKHZvaWQpOwoKCmlu
dCBtYWluKHZvaWQpCnsKICAgaW50IGEsIGIsIGM7CgogICBhID0gZigpOwogICAKICAgaWYgKGEp
CiAgIHsKICAgICAgIGIgPSAxMDsKICAgfQoKICAgaWYgKGYoKSkKICAgewogICAgICAgYyA9IDE1
MTsKICAgfQoKICAgaWYgKGEpCiAgICAgICByZXR1cm4gYjsKICAgcmV0dXJuIDA7Cn0KCg==


             reply	other threads:[~2001-12-06 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06  9:16 thutt [this message]
2002-04-26  1:56 rth
2002-04-29  5:56 Taylor Hutt
2002-04-29 10:46 Richard Henderson

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=20011206170914.25904.qmail@sources.redhat.com \
    --to=thutt@vmware.com \
    --cc=gcc-gnats@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).