This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
other/10138: -Wuninitialized could catch const* parameters
- From: Hallvard B Furuseth <h dot b dot furuseth at usit dot uio dot no>
- To: gcc-gnats at gcc dot gnu dot org
- Date: Tue, 18 Mar 2003 18:40:24 +0100
- Subject: other/10138: -Wuninitialized could catch const* parameters
>Number: 10138
>Category: other
>Synopsis: -Wuninitialized could catch const* parameters
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Tue Mar 18 17:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Hallvard B Furuseth
>Release: 3.2
>Organization:
University of Oslo
>Environment:
System: SunOS bombur.uio.no 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10
Architecture: sun4
host: sparc-sun-solaris2.8
build: sparc-sun-solaris2.8
target: sparc-sun-solaris2.8
configured with: ../gcc-3.2/configure --prefix=/usit/bombur/hbf --enable-threads --enable-version-specific-runtime-libs --enable-languages=c
>Description:
A pointer to const parameter is almost always an input parameter
to a function, so -Wuninitialized could warn if it has not been
initialized. (The function could cast away const on the parameter,
but I've never seen the parameter being modified afterwards.)
>How-To-Repeat:
gcc -Wuninitialized -O -S a.c
int atoi(const char *);
int foo()
{
char buf[10];
return atoi(buf);
}
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: