TL:DR: minimize randomness, group variables by access frequency, and unroll loops if your compiler doesn’t do that already
Hardware-Aware Coding: CPU Architecture Concepts Every Developer Should Know
Submitted 10 months ago by abhi9u@lemmy.world to technology@lemmy.world
https://blog.codingconfessions.com/p/hardware-aware-coding
Comments
pixeltree@lemmy.blahaj.zone 10 months ago
call_me_xale@lemmy.zip 10 months ago
tl;dr tl;dr: use a modern compiler.
bejean@lemmy.world 10 months ago
Do any compilers NOT unroll loops in high optimization modes? I was under three impression this was usually unnecessary.
pixeltree@lemmy.blahaj.zone 10 months ago
No clue, I was just frustrated with how much useless extended metaphor was in the article and thought I’d save people some time
InverseParallax@lemmy.world 10 months ago
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.
ElPussyKangaroo@lemmy.world 10 months ago
What about Claude-Aware coding tho? /s
call_me_xale@lemmy.zip 10 months ago
Can we just not with the AI-generated illustrations?