Re: Compiler Design in C How about it?

In article <1990Jun4.044858.15066@esegue.segue.boston.ma.us> Mark Henderson <markh@squirrel.labs.tek.com> writes:
>In article <1990Jun1.194941.5781@esegue.segue.boston.ma.us> Preston Briggs <preston@rice.edu> writes:
>>[quoting Holub, using unsafe optimizations is an OK idea]
>
>Fact is, historically the optimizer is where compiler writers have hung
>themselves. I've used several commercial compilers for which I often had to
>turn off the optimization to get them to handle some pretty mundane code
>properly. (I suppose there is no need to mention company names here).


I've heard quite the opposite from Richard Stallman about his GCC
compiler, paradoxically enough: he claims that there are more bugs in
"gcc" as opposed to "gcc -O" since most of the time gcc users turn the
optimizer on (and hence have uncovered the optimizer bugs) and also
that the optimizer tends to hide a few bugs in the code generator by
never letting it generate the bad code in the first place!
--
Byron Rakitzis. (tbrakitz@phoenix.Princeton.EDU)
--

Return to the comp.compilers page.
Search the comp.compilers archives again.