Re: compiler bugs

Tony Finch <>
29 Apr 2009 15:31:21 +0100 (BST)

          From comp.compilers

Related articles
[6 earlier articles]
Re: compiler bugs (Louis Krupp) (2009-04-28)
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)
[10 later articles]
| List of all articles for this month |

From: Tony Finch <>
Newsgroups: comp.compilers
Date: 29 Apr 2009 15:31:21 +0100 (BST)
Organization: dotat labs
References: 09-04-072
Keywords: errors
Posted-Date: 29 Apr 2009 11:45:04 EDT

Sid Touati <> wrote:
>How can a simple programmer detect a bug in a compiler ? is there some
>well known verification techniques ?

There's a brillant paper by Eric Eide and John Regehr from the University
of Utah where they use a clever variant of fuzz testing to find bugs in
the way compilers implement C's volatile storage qualifier. They use
a code generator to create random programs, and they instrument their
execution to find out their memory access patterns. They detect compiler
bugs by compiling the programs with different optimisation levels and
seeing when the access patterns differ.

f.anthony.n.finch <>

Post a followup to this message

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