Re: compiler bugs

"Derek M. Jones" <>
Wed, 29 Apr 2009 16:15:17 +0100

          From comp.compilers

Related articles
[7 earlier articles]
Re: compiler bugs (Jonathan Thornburg) (2009-04-28)
Re: compiler bugs (2009-04-28)
Re: compiler bugs (George Peter Staplin) (2009-04-28)
Re: compiler bugs (Marco van de Voort) (2009-04-29)
Re: compiler bugs (2009-04-29)
Re: compiler bugs (Tony Finch) (2009-04-29)
Re: compiler bugs (Derek M. Jones) (2009-04-29)
Re: compiler bugs (glen herrmannsfeldt) (2009-04-29)
Re: compiler bugs (Jeremy J Starcher) (2009-04-29)
Re: compiler bugs (Walter Banks) (2009-04-30)
Re: compiler bugs (Chris F Clark) (2009-04-30)
Re: compiler bugs (2009-05-01)
Re: compiler bugs (Gene) (2009-05-01)
[9 later articles]
| List of all articles for this month |

From: "Derek M. Jones" <>
Newsgroups: comp.compilers
Date: Wed, 29 Apr 2009 16:15:17 +0100
References: 09-04-072 09-04-080
Keywords: testing
Posted-Date: 29 Apr 2009 11:45:51 EDT


>> How can a simple programmer detect a bug in a compiler ? is there some
>> well known verification techniques ?
> If there is, I don't know it. Compiler writers generally test their
> compilers quite hard - there are various test suites of source code
> available, and all serious compiler writing organisations will develop
> test sets of their own and expand them as they fix bugs - but there is
> no simple and all-embracing method.

The part of the test suites (eg, Perennial) that compiler writers
uses is often only the part that checks the syntax and semantics.
While code generation stress testers might be included they are
used less frequently.

for a discussion of one area where compiler correctness seems to be

Post a followup to this message

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