3 ms·
I do; low level, OS and library code should be both. It's not an either or; you start with the correct code (and code to verify), then if needs be you optimize.
by Cthulhu_ 6y ago
I do; low level, OS and library code should be both. It's not an either or; you start with the correct code (and code to verify), then if needs be you optimize.
- ndr 6y agoHow is this not confirming the point you're replying to?
- wongarsu 6y agoSo you're saying maximum priority is correctness, and performance second place? Because if you don't have correctness you can't "start with correct code"
- 0xTJ 6y agoIf you have a broken compiler, you can have broken generated code, and not even know it. This isn't about whether or not your C code is correct, this is about whether the assembly that's generated matches the behavior in your code.