This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/10138] -Wuninitialized could catch uninitialized arrays
- From: "h dot b dot furuseth at usit dot uio dot no" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 May 2003 16:38:24 -0000
- Subject: [Bug other/10138] -Wuninitialized could catch uninitialized arrays
- 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=10138
------- Additional Comments From h.b.furuseth@usit.uio.no 2003-05-26 16:38 -------
Subject: Re: [Bug other/10138] -Wuninitialized could catch uninitialized arrays
pinskia@physics.uc.edu writes:
> Change title to reflect real bug.
Oops, I have reported several suggestions which should be split up:
1) It could report use of uninitialized arrays as you say,
2) it could report pointers to uninitialized variables passed
as const* arguments - as I said, that's almost always an error:
void use(const int *);
void foo(void)
{
int i;
use(&i);
}
3) Finally it could report the combination, as in my original example.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.