abhi9u@lemmy.world to Technology@lemmy.worldEnglish · 1 month agoHardware-Aware Coding: CPU Architecture Concepts Every Developer Should Knowblog.codingconfessions.comexternal-linkmessage-square8fedilinkarrow-up174arrow-down16
arrow-up168arrow-down1external-linkHardware-Aware Coding: CPU Architecture Concepts Every Developer Should Knowblog.codingconfessions.comabhi9u@lemmy.world to Technology@lemmy.worldEnglish · 1 month agomessage-square8fedilink
minus-squarebejean@lemmy.worldlinkfedilinkEnglisharrow-up4·1 month agoDo any compilers NOT unroll loops in high optimization modes? I was under three impression this was usually unnecessary.
minus-squarepixeltree@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up3·1 month agoNo clue, I was just frustrated with how much useless extended metaphor was in the article and thought I’d save people some time
minus-squareInverseParallax@lemmy.worldlinkfedilinkEnglisharrow-up1·1 month agoReally depends on the target, llvm goes between unrollimg and vectorizing cleanly, to unrollimg to a ludicrous degree, to refusing to unroll period. Some of it is subtarget specific, but sometimes it’s just weird. Gcc is evil incarnate, all it’s passes are at war with each other, loop Canon form often broke vectorization and even unrolling period.
Do any compilers NOT unroll loops in high optimization modes? I was under three impression this was usually unnecessary.
No clue, I was just frustrated with how much useless extended metaphor was in the article and thought I’d save people some time
Really depends on the target, llvm goes between unrollimg and vectorizing cleanly, to unrollimg to a ludicrous degree, to refusing to unroll period.
Some of it is subtarget specific, but sometimes it’s just weird.
Gcc is evil incarnate, all it’s passes are at war with each other, loop Canon form often broke vectorization and even unrolling period.