compiler bugs

Sid Touati <SidTouati@inria.fr>
Mon, 27 Apr 2009 14:42:19 +0200

          From comp.compilers
Related articles
Re: Compiler bugs Peter-Lawrence.Montgomery@cwi.nl (2002-01-05)
Re: Compiler bugs christian.bau@cbau.freeserve.co.uk (Christian Bau) (2002-01-05)
Re: Compiler bugs chase@world.std.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 r3jjs@yahoo.com (Jeremy J Starcher) (2009-04-28)
Re: compiler bugs lkrupp@indra.com (Louis Krupp) (2009-04-28)
Re: compiler bugs jonathan@nitrogen.astro.indiana.edu (Jonathan Thornburg) (2009-04-28)
Re: compiler bugs jgd@cix.compulink.co.uk (2009-04-28)
Re: compiler bugs georgeps@xmission.com (George Peter Staplin) (2009-04-28)
[44 later articles]
| List of all articles for this month |
From: Sid Touati <SidTouati@inria.fr>
Newsgroups: comp.compilers
Date: Mon, 27 Apr 2009 14:42:19 +0200
Organization: INRIA - CR Paris-Rocquencourt
Keywords: errors, question
Posted-Date: 28 Apr 2009 05:11:13 EDT

How can a simple programmer detect a bug in a compiler ? is there some
well known verification techniques ?


I am afraid that many bugs are hidden inside compiler activated with
sophisticated optimisation options, and few people can detect them: when
a user program does not work, we usually think that the problem comes
from the program itself, not from the compiler nor from the processor.


On the other hand, when a compilation flag is on and the program
crashes, we usually think that the bug comes from the compiler not from
the program...


Post a followup to this message

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