3 ms·
This is the correct answer, plus add loop unrolling etc. It is simply not possible to write an optimizing compiler in which the evaluation order is truly indet
by atq2119 5y ago
This is the correct answer, plus add loop unrolling etc.
It is simply not possible to write an optimizing compiler in which the evaluation order is truly indeterminate yet always the same.
- tsimionescu 5y agoI was claiming it could be left implementation defined instead of unspecified. That way, code for particular platforms could be evaluated in different order, but it would always be deterministic for a particular compiler.
- vnorilo 5y agoThe optimized evaluation order would depend on the situation near at the call site, not the architecture or platform.
- tsimionescu 5y agoThe GP that my post was replying to was claiming it was arch dependent, and I was pointing out that, if it had been, they would have likely not left it unspecified. So, I think you and I are in agreement.