3 ms·
When a problem is described as an optimizer issue, it usually means that the code is making some unsound assumptions that happen to be true when compiling witho
by gjm11 16y ago
When a problem is described as an optimizer issue, it usually means that the code is making some unsound assumptions that happen to be true when compiling without optimization. Of course it's easier on the programmer's ego to blame it on the compiler...
(I haven't looked at this particular issue; maybe it really is a compiler bug. But the odds are against it.)
- istvanp 16y agoMight be true in general, but when the creator of PHP says it's a compiler issue it's hard to 2nd guess. He also later added: We still need to fix the code to make it immune to compiler switches.
- naz 16y agohttp://en.wikipedia.org/wiki/Argument_from_authority http://en.wikipedia.org/wiki/Argument_from_authority
- SimHacker 16y ago"I'm not a real programmer. I throw together things until it works then I move on. The real programmers will say "Yeah it works but you're leaking memory everywhere. Perhaps we should fix that."" -Rasmus Lerdorf When you attempt to make an argument from authority, at least choose someone who has some credibility to use as an authority.
- marshray 16y agoWe still need to fix the code to make it immune to compiler switches. In other words, "We know that our code is buggy and it is relying on undefined behavior." I.e., this developer knows it's a problem with his code, not the compiler, but he phrases it as if the "compiler switches" are the things causing the problems. This is classic developer arrogance and immaturity. Thank God I don't rely on his software for anything important.