3 ms·
>It's a nice reminder that for the ultimate performance, there is no substitute for knowing exactly what the assembler is doing. I didn't realize viewing the a
by Arnavion 5y ago
>It's a nice reminder that for the ultimate performance, there is no substitute for knowing exactly what the assembler is doing.
I didn't realize viewing the assembly of a compiled binary was something reserved for C. Someone should tell rust.godbolt.org that it's not supposed to exist.
- samhw 5y agoI think their point is that C is sufficiently close to assembler that you know exactly what assembly any given line of C will produce. This is an old canard which is not really true (https://zenhack.net/2015/08/02/c-is-not-portable-assembly.html https://zenhack.net/2015/08/02/c-is-not-portable-assembly.ht...), but it's common among people who derive a sense of identity from writing C.
- dahfizz 5y agoGo read the second place C entry[1]. Its a JIT for assembly code. [1] https://codegolf.stackexchange.com/questions/215216/high-throughput-fizz-buzz/#answer-236737 https://codegolf.stackexchange.com/questions/215216/high-thr...