lysdexic@programming.dev to Programming@programming.devEnglish · 1 year agoPush Ifs Up And Fors Downmatklad.github.ioexternal-linkmessage-square18fedilinkarrow-up138arrow-down15cross-posted to: rust@zorg.socialhackernews@lemmy.smeargle.fanshackernews@derp.foo
arrow-up133arrow-down1external-linkPush Ifs Up And Fors Downmatklad.github.iolysdexic@programming.dev to Programming@programming.devEnglish · 1 year agomessage-square18fedilinkcross-posted to: rust@zorg.socialhackernews@lemmy.smeargle.fanshackernews@derp.foo
minus-squarepipe01@lemmy.pipe01.netlinkfedilinkarrow-up1·1 year agoYou still need to read the variable in each iteration, but the cost of that is probably negligible
minus-squareRyan@programming.devlinkfedilinkEnglisharrow-up3·edit-21 year agoModern optimizing compilers are magical. I would need to check assembly but I would actually expect the if to be hoisted out of the loop entirely to relieve pressure on the branch predictor.
You still need to read the variable in each iteration, but the cost of that is probably negligible
Modern optimizing compilers are magical. I would need to check assembly but I would actually expect the if to be hoisted out of the loop entirely to relieve pressure on the branch predictor.