From: Dmitry Antipov <antipov@dev.rtsoft.ru>
To: gcc@gcc.gnu.org
Subject: Re: Dubious "'foo' might be used uninitialized in this function" message
Date: Wed, 15 Dec 2004 09:00:00 -0000 [thread overview]
Message-ID: <41C009AA.4020700@dev.rtsoft.ru> (raw)
In-Reply-To: <41BF1C0A.6060100@codesourcery.com>
Nathan Sidwell wrote:
> Dmitry Antipov wrote:
>
>> w.c: In function `f':
>> w.c:5: warning: 'z' might be used uninitialized in this function
>>
>> which is not true.
>
> 'tis true too, just here.
> return x + y + z;
Oops. That's my mistake, both examples are incorrect :-(. It should be
(with line numbers, for referencing lines)
1 #include <unistd.h>
2
3 int f (int x, int y)
4 {
5 int z;
6
7 if (x)
8 z = getppid ();
9 y = getpid ();
10 if (x)
11 y += z;
12 return x + y;
13 }
in the first case and
1 #include <unistd.h>
2
3 int f (int x, int y)
4 {
5 int z;
6
7 if (x)
8 z = getppid ();
9 y = getpid ();
10 y += z;
11 return x + y;
12 }
in the second, respectively.
> read the documentation for -Wuninitialized, which will explain
> why it can't get all the cases correct.
I've taken a look through 3.4.3. docs online. The docs describes
two different cases:
> {
> int x;
> switch (y)
> {
> case 1: x = 1;
> break;
> case 2: x = 4;
> break;
> case 3: x = 5;
> }
> foo (x);
> }
>
> If the value of y is always 1, 2 or 3, then x is always initialized,
but GCC doesn't know this.
This sample probably means that we have something like:
void bar (int y)
{
int x;
switch (y)
{
case 1: x = 1;
break;
case 2: x = 4;
break;
case 3: x = 5;
}
foo (x);
}
If 'bar()' has the global scope (can be called from another modules), it's
impossible to predict the value of 'y', and we should warn always. But, if
the bar is 'static', we can look through all calls of the 'bar()' and do
the following check for each call:
if (argument of 'bar()' is a compile-time constant) {
if (argument of bar is not 1, 2, or 3)
warn ();
} else
warn ();
IMHO, this kind of check may be really useful.
The second example from documentation
> {
> int save_y;
> if (change_y) save_y = y, y = new_y;
> ...
> if (change_y) y = save_y;
> }
is similar to my sample #1 (except that this example implicitly assumes
that 'change_y' isn't changed in the middle code marked as '...').
Probably that's the case which is described with "GCC is not smart enough to
see all the reasons why the code might be correct" words in the docs :-).
>> Is it reasonable to learn GCC do more analysis in attempt to avoid
>> warning in this case ? How is it complex ?
>
>
> it gets as complex as the halting problem :)
Really ? Why ?
Dmitry
next prev parent reply other threads:[~2004-12-15 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 15:23 Dmitry Antipov
2004-12-14 16:40 ` E. Weddington
2004-12-14 17:00 ` Nathan Sidwell
2004-12-15 9:00 ` Dmitry Antipov [this message]
2004-12-15 10:02 ` Nathan Sidwell
2004-12-15 12:06 ` Robert Dewar
2004-12-15 17:33 ` Joe Buck
2004-12-15 18:03 ` Dave Korn
2004-12-15 18:09 ` Robert Dewar
2004-12-15 17:33 ` Florian Weimer
2004-12-15 17:34 ` Robert Dewar
2004-12-15 17:52 ` Florian Weimer
2004-12-15 18:00 ` Robert Dewar
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=41C009AA.4020700@dev.rtsoft.ru \
--to=antipov@dev.rtsoft.ru \
--cc=gcc@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).