3 ms·
That doesn't really help with the compiler optimization aspect : A typical use of the range information would be to unroll the loop - in which case there's no a
by anarazel 5y ago
That doesn't really help with the compiler optimization aspect : A typical use of the range information would be to unroll the loop - in which case there's no addition to trap on anymore.
- tsimionescu 5y agoTo be fair, if you want to make sure that loop is unrolled even in the presence of -fwrapv, writing it as for (int i=0; i < 16; i++) {/* use i+param */} is a very simple change for you to make even today. You'll have to make much uglier changes to code if you're at the level of optimization where loop unrolling really matters for your code on a modern processor.