2 ms·
I know. I've used C for two decades, I write it professionally today. Some bugs end up being extremely difficult to debug. I accept that as a fact of life; i
by foxfluff 5y ago
I know. I've used C for two decades, I write it professionally today.
Some bugs end up being extremely difficult to debug. I accept that as a fact of life; in exchange, we get pretty decent performance.
Guess what I do when there's a bug I have a hard time pinning down? Recompile with optimizations turned off.
By the way, I don't think I have ever witnessed a bug caused by an accidentally-infinite loop getting optimized out. So making that almost-never-happens situation easier to fix is not worth trading any optimizations for, imo. I'd rather just get a warning from compiler/static analyzer (if the code isn't the way it is due to macro expansion).