state of a typical C compiler, 1998
-
state of a typical C compiler, 1998
@joe "The famous Pentium divide bug (we did not catch it but we could have)": well aren't they sophisticated.
-
@joe btw-- this is the same person who, more than 30 years earlier, coined the term "peephole optimization" 👀
@joe I exchanged a few emails with him many years back. but I think, clearly, most of us here should have bought him a couple beers
-
state of a typical C compiler, 1998
@joe I love that the experience of reading that table is like "sure, I can see how that would happen" and then you get to the TWENTY MINUTE COMPILE TIME. The "server crash" one is fun too.
-
@joe btw-- this is the same person who, more than 30 years earlier, coined the term "peephole optimization" 👀
-
state of a typical C compiler, 1998
@joe the heck is -!0
-
@joe the heck is -!0
@joe if you put that in your code, you deserve a compiler error
-
@joe we can see exactly how it happens
-
@joe the heck is -!0
@ratsnakegames not much, what’s -! With you
-
state of a typical C compiler, 1998
@joe "Twenty-minute compile time" is so perfect and understated
-
@joe "Twenty-minute compile time" is so perfect and understated
@joe of course with modern OOO processors this would be like 0.2 seconds and would go unnoticed
-
@joe of course with modern OOO processors this would be like 0.2 seconds and would go unnoticed
-
-
@joe of course with modern OOO processors this would be like 0.2 seconds and would go unnoticed
-
@cr1901 singularity (1 million parentheses)
-
state of a typical C compiler, 1998
@joe "several compiler crashes"
-
@joe "several compiler crashes"
@joe crashing multiple times in a single run implies some advanced error handling
-
@joe of course with modern OOO processors this would be like 0.2 seconds and would go unnoticed
-
state of a typical C compiler, 1998
@joe@f.duriansoftware.com okay I'm curious about the original source for this and the reason as to why these happen. Some are obvious but how does
if (sizeof(char)+d) f(d)cause an illegal instruction to be emitted? -
-
@joe of course with modern OOO processors this would be like 0.2 seconds and would go unnoticed