Apple's compiler gives this (even with no 'warning' flags applied)
I don't have the original anymore (just a one-off test) but
#SelectExpand
1#include <stdio.h>
2
3#define LIMIT 1000
4
5unsigned int array
[LIMIT
];
6
7int main
(void)
8{
9 int i
;
10
11 for(i
=0;i
<10;i
++);
12 array
[LIMIT
] = i
;
13
14 //just to make sure the whole thing doesn't get optimized away
15 for(i
=0;i
<LIMIT
;i
++)
16 printf("%d\n",array
[i
]);
17
18 return 0;
19}
run through Slackware current gcc version 5.5.0 gave an error as
"warning: array subscript is above array bounds [-Warray-bounds]"
with -O2 -Wall options. Changing line 12 to read
array[4] = i;
got it to compile with no warnings or errors
The latest DJGPP has gcc version 9.3.0 (!) which gave these warnings
t.c: In function 'main':
t.c:12:2: warning: this 'for' clause does not guard... [-Wmisleading-indentation]
12 | for(i=0;i<10;i++);
| ^~~
t.c:13:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'for'
13 | array[LIMIT] = i;
| ^~~~~
t.c:13:8: warning: array subscript 1000 is above array bounds of 'unsigned int[1000]' [-Warray-bounds]
13 | array[LIMIT] = i;
| ~~~~~^~~~~~~
t.c:6:14: note: while referencing 'array'
6 | unsigned int array[LIMIT];
| ^~~~~
OTOH, I seem to remember an old ALLEGRO.TXT as saying something about such a loop being used for a delay
"If the compiler complains, try changing it to
for(i=0;i<1000;i++) {};
to beat the compiler into submission."
]]>
