2 ms·
sure, but ivdep is supposed to explicitly tells the compiler that there are no loop carried dependencies between iterations, so iteration i-1 couldn't possibly
by gpderetta 7y ago
sure, but ivdep is supposed to explicitly tells the compiler that there are no loop carried dependencies between iterations, so iteration i-1 couldn't possibly write to a memory location read by iteration i.
- BeeOnRope 7y agoAh sorry, I read your ivdep sentence and the second part of your post as independent, i.e,. that the compiler should be able to assume this (even without ivdep). I realize now you were saying "[With ivdep] and in this specific case, the compiler should be able to assume..." It makes sense now.