The point is that the compiler should see that the run-time value of i is
_obviously_never_negative_ and as such the warning is total and utter
The compiler actually does end up doing some of that kind of analysis when
optimizing, since it is required for some of the loop optimizations
anyway. But the warning is emitted before the analysis has taken place.
In other words, gcc is stupidly warning about something that is obviously
not an error. And it is obviously not an error because:
- array indexes are "int". They aren't size_t, and never have been. Thus
it is _correct_ to use "int" for the index. You write
and you do NOT write
and anybody who writes 'array[5UL]' is considered a stupid git and a
geek. Face it.
Claiming that you should index an array with a size_t is crap.
- the way this has traditionally always been done is the example I
posted. Warning about correct, obvious, and traditional code is WRONG,
if it causes the programmer to have to write something _less_ obvious
just to make a stupid compiler warning go away makes the warnign WORSE
And yes, gcc could do the work necessary to only give the warning if it
actually has reason to believe that the code is wrong. As it is, it gives
the warning for code that is good.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/