|> On Mon, 24 Feb 2003, Andreas Schwab wrote:
|> > But that's not the point. It's the runtime value of i that gets converted
|> > (to unsigned), not the compile time value of COUNT. Thus if i ever gets
|> > negative you have a problem.
|> 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
This requires a complete analysis of the loop body, which means that the
warning must be moved down from the front end (the common type of the
operands only depends on the type of the operands, not of any current
value of the expressions).
|> 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
|> int array;
|> and you do NOT write
|> int array[5UL];
|> and anybody who writes 'array[5UL]' is considered a stupid git and a
|> geek. Face it.
But array[-1] is wrong. An array can never have a negative index (I'm
*not* talking about pointers).
-- Andreas Schwab, SuSE Labs, firstname.lastname@example.org SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." - 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/