What every compiler writer should know about programmers [pdf]
One of the things this person misses is a lot of these are undefined <i>with the explicit goal to let compiler authors take advantage of them</i>.<p>So his real argument is with the C committee for not defining these things the way he wants them.  His claim that the behavior of what should happen is obvious is pretty strange (IE &quot;it should do exactly whatever the compiler is trying to prove it doesn&#x27;t&quot;)<p>It&#x27;s essentially a complaint that compiler authors should follow a mystical spirit of C that he seems to have in his head.<p>(Plus, you know, he&#x27;s kind of a dick about it all)<p>I read things like &quot;We had plans to turn this optimization into a production feature, but eventually
realized that the GCC maintainers only care about certain benchmarks
and treat production programmers as adversaries that deserve getting their code
broken.
...
The current GCC and Clang maintainers suggest that we should convert
programs to “C”. How would that turn out for Gforth?&quot;<p>I was intrigued, so i went looking for the mailing list discussion where the gcc or clang people suggested this or where any of this happened.<p>I can&#x27;t find it.  
On either set of mailing lists.
I searched for gforth, i searched for anton, etc
Nothing.