2 ms·

You seem to be arguing against a straw-man, sir. The OP simply said that the chances of finding a compiler bug are small. You seem to have found a few minor bu

by ksk 9y ago

You seem to be arguing against a straw-man, sir. The OP simply said that the chances of finding a compiler bug are small. You seem to have found a few minor bugs, and that's cool, but how does that change the fact that chances an average C developer finding a compiler bug are minuscule? There are probably around a million C developers, do we even have one compiler bug per 10 developers?

arghwhat 9y ago
> You seem to have found a few minor bugs, and that's cool I'm sorry, how are total miscompilations and memory corruptions "minor bugs"? I am arguing against the mentality of dismissing compiler bugs, with the idea that "you will never hit one". Hence my examples of when I hit them during something as high-level as web development. I am not arguing that you'll hit such bug every day, or even every month. I only have myself and those around me as reference. I have been a software developer for less than 10 years, but with the current total, I have been hitting a few "lower layer" (vm, stdlib, compiler, kernel, hardware) bugs a year. Maybe I'm just "unlucky". If you want to find real numbers, take a look at GCC/LLVM/libstdc++/glibc/linux bug tracker statistics. I'm sure you will be surprised.