A constant reference to an array element past the end of the array does not
generate an error. Included are the output from gcc -v and a test program that
mimics the real-world case where the coding error corrupted the stack:
Using built-in specs.
Target: i586-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,f95,java,ada --disable-checking
--with-gxx-include-dir=/usr/include/c++/4.0.2 --enable-java-awt=gtk
--disable-libjava-multilib --with-slibdir=/lib --with-system-zlib
--enable-shared --enable-__cxa_atexit --without-system-libunwind
--host=i586-suse-linux
Thread model: posix
gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)
Test Program:
=============
int sub1(int);
int main(int argc, char **argv) {
int i,j = 0;
i = sub1(j);
return i;
}
int sub1(int j ) {
int b[13];
b[13] = j;
return 0;
}
--
Summary: Constant array index past end does not generate compile-
time error
Product: gcc
Version: 4.0.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: Larry dot Finger at lwfinger dot net
GCC host triplet: i586-suse-linux
GCC target triplet: i586-suse-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24728
