Re: Justifying Optimization

In general I agree with John, our famous mod :-)


MICHAEL DILLON <mike.dillon@lmco.com> schreibt:
>Developers are stating that optimized code produces errors


This statement is incorrect, since buggy or misleaded optimizers /can/ produce
errors, as well as buggy or misleaded compilers can produce errors, even if
they do no optimization.


>and makes debugging more difficult.


This is (almost ;-) true. So why do you insist in debugging optimized code,
when OTOH you suppose that both the optimized and non-optimized code will
produce exactly the same results???


IMO the validation of the source code should be separated from the validation
of the compiler specific optimization.


And finally, what would you do if the outcome of the optimized and
non-optimized versions differ? Would you introduce workarounds into your source
code, to outwit bugs in the compiler optimization??? Is it this task which you
are paid for? What if these workarounds will no more work with the next
compiler version?


DoDi

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