loop optimization is intimately tied to being able to assume the index doesn't wrap and exit the array, no? GCC says: > -faggressive-loop-optimizations This o

loop optimization is intimately tied to being able to assume the index doesn't wrap and exit the array, no? GCC says: > -faggressive-loop-optimizations This option tells the loop optimizer to use language constraints to derive bounds for the number of iterations of a loop. This assumes that loop code does not invoke undefined behavior by for example causing signed integer overflows or out-of-bound array accesses. The bounds for the number of iterations of a loop are used to guide loop unrolling and peeling and loop exit test optimizations.