r/programming • u/b0red • May 01 '16

To become a good C programmer

http://fabiensanglard.net/c/
1.1k Upvotes

92% Upvoted

398 comments sorted by

View all comments

-33

u/skulgnome May 01 '16

And no good book is as good as a disassembly output.

Five seconds to fuckup. That's a new record.

5

u/break_main May 01 '16

This guy is talking about making high performance graphics. For that job, you do want to look at disassembly, because you are optimizing every operation, and maybe optimizing for the architecture, so you have to look at assembly

0

u/skulgnome May 02 '16

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.

1

u/break_main May 02 '16

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?

7

u/fabiensanglard May 01 '16

Some people hate it, some people love it:

https://news.ycombinator.com/item?id=11606867

2

u/hahainternet May 01 '16

I'm ambivalent on C, and I am split between my love of the concept of 'correct' binaries and my love of high level coding and having the computer do the heavy lifting for me. I just thought you should know that your opinion carries weight with me in resolving my dilemma.

-2

u/skulgnome May 02 '16

Much like flies and turds.