|Re: Compiler bugs Peter-Lawrence.Montgomery@cwi.nl (2002-01-05)|
|Re: Compiler bugs firstname.lastname@example.org (Christian Bau) (2002-01-05)|
|Re: Compiler bugs email@example.com (David Chase) (2002-01-14)|
|compiler bugs SidTouati@inria.fr (Sid Touati) (2009-04-27)|
|Re: compiler bugs DrDiettrich1@aol.com (Hans-Peter Diettrich) (2009-04-28)|
|Re: compiler bugs firstname.lastname@example.org (Jeremy J Starcher) (2009-04-28)|
|Re: compiler bugs email@example.com (Louis Krupp) (2009-04-28)|
|Re: compiler bugs firstname.lastname@example.org (Jonathan Thornburg) (2009-04-28)|
|Re: compiler bugs email@example.com (2009-04-28)|
|RE: compiler bugs firstname.lastname@example.org (Quinn Tyler Jackson) (2009-04-28)|
|Re: compiler bugs email@example.com (George Peter Staplin) (2009-04-28)|
|Re: compiler bugs firstname.lastname@example.org (Marco van de Voort) (2009-04-29)|
|[18 later articles]|
|From:||Jeremy J Starcher <email@example.com>|
|Date:||Tue, 28 Apr 2009 17:15:54 GMT|
|Posted-Date:||28 Apr 2009 14:50:58 EDT|
On Mon, 27 Apr 2009 14:42:19 +0200, Sid Touati wrote:
> How can a simple programmer detect a bug in a compiler ? is there some
> well known verification techniques ? ...
Since you didn't say what language or compiler you are using, I can only
answer in very general terms.
In some circumstances, optimizers are known to break code. Sometimes by
optimizing away side effects. Sometimes causing heisen-bugs by changing
the order of evaluations and sometimes by tripping over "clever" code.
That said, when I come across a problem, I always assume the bug is in my
code until I can provide a test case that clearly demonstrates that the
compiler itself is at fault. Then I have someone else review my code to
make sure I'm not being an idiot.
Return to the
Search the comp.compilers archives again.