From: | Robert A Duff <bobduff@shell01.TheWorld.com> |
Newsgroups: | comp.compilers |
Date: | Tue, 19 May 2009 20:58:07 -0400 |
Organization: | The World Public Access UNIX, Brookline, MA |
References: | 09-04-072 09-04-086 09-05-010 09-05-022 09-05-028 09-05-038 09-05-039 09-05-050 09-05-055 09-05-065 09-05-069 |
Keywords: | optimize, debug |
Posted-Date: | 20 May 2009 09:59:05 EDT |
anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
> "Christopher Glaeser" <cdg@nullstone.com> writes:
>>Even a simple bug fix to a new release in a compiler
>>can affect the behavior of C programs that have undefined behavior.
>
> Different releases are a different issue than turning optimization on,
> although changing behaviour between releases is not desirable, either.
What about portability to a completely different compiler on a
completely different machine? Do you expect your program to behave
the same?
I think you're attacking the wrong folks, here. If optimizers can
affect the behavior of programs, that's primarily the fault of the
language designer, not the compiler writer.
Language designers ought to minimize such cases. Ada has fewer cases of
undefined behavior than C. Java has even fewer.
- Bob
Return to the
comp.compilers page.
Search the
comp.compilers archives again.