This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/11182] gcc should warn when assigning unassigned variables
- From: "falk dot hueffner at student dot uni-tuebingen dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Jun 2003 17:14:43 -0000
- Subject: [Bug c++/11182] gcc should warn when assigning unassigned variables
- References: <20030613045823.11182.charles@kde.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11182
------- Additional Comments From falk.hueffner@student.uni-tuebingen.de 2003-06-14 17:14 -------
Subject: Re: gcc should warn when assigning unassigned variables
"pinskia@physics.uc.edu" <gcc-bugzilla@gcc.gnu.org> writes:
> With this source: int f(){ int x; int y = x; return y; } I get a
> warning at -O1 -W -Wall with 2.95.2, 3.1, and the mainline (). Do
> you want the warning at -O0 if you do this is a know problem?
I suppose it's rather another instance of
int f() { int x = x; return x; }
i. e., no warning when initializing a variable with itself, which is
already c++/5284 and probably some more.