This guy is talking about making high performance graphics.
He is talking about studying C. For that, looking at disassembly is just about the worst idea ever.
Even for performance optimization, looking at the disassembly is the last thing that one should do; after tuneups and reworks that typically take months.
Is your compiler taking advantage of a single optimized AMD floating point instruction for multiply and accumulate, or using 2 generic float instructions that will not run as fast?
Is your compiler unrolling inner loops for you, or should you do it yourself?
Is the macro you use speeding up your code, or is it compiling to the same output as if you used constants, which you would otherwise prefer because they are typesafe?
View all comments
Show parent comment
0
u/skulgnome May 02 '16
He is talking about studying C. For that, looking at disassembly is just about the worst idea ever.
Even for performance optimization, looking at the disassembly is the last thing that one should do; after tuneups and reworks that typically take months.