This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/36296] wrong warning about potential uninitialized variable
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 May 2008 07:31:04 -0000
- Subject: [Bug middle-end/36296] wrong warning about potential uninitialized variable
- References: <bug-36296-16207@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from pinskia at gcc dot gnu dot org 2008-05-28 07:31 -------
(In reply to comment #5)
> BTW, the i = i trick
it only works in the initializer and not as a statement after the fact.
That is:
#include <assert.h>
int foo (int x)
{
int y = y;
assert (x == 0 || x == 1);
if (x == 0)
y = 1;
else if (x == 1)
y = 2;
return y;
}
Will work, also with the jump threading, GCC should be able to figure out that
y is always inlined (except when -DNDEBUG is used).
-- Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36296