[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [csmith-dev] Fwd: Re: csmith test harness help

To: John Regehr <regehr@cs.utah.edu>
Subject: Re: [csmith-dev] Fwd: Re: csmith test harness help
From: Andy Lester <andy@petdance.com>
Date: Wed, 13 Apr 2011 22:43:11 -0500
Cc: csmith-dev@flux.utah.edu
In-reply-to: <4DA66CB3.2060705@cs.utah.edu>
List-archive: </listarchives/csmith-dev>
List-help: <mailto:csmith-dev-request@flux.utah.edu?subject=help>
List-id: Csmith Development Mailing List <csmith-dev.flux.utah.edu>
List-post: <mailto:csmith-dev@flux.utah.edu>
List-subscribe: <http://www.flux.utah.edu/mailman/listinfo/csmith-dev>, <mailto:csmith-dev-request@flux.utah.edu?subject=subscribe>
List-unsubscribe: <http://www.flux.utah.edu/mailman/listinfo/csmith-dev>, <mailto:csmith-dev-request@flux.utah.edu?subject=unsubscribe>
References: <4DA66CB3.2060705@cs.utah.edu>

> Nope!  But let's be clear: although Csmith includes a static analyzer,
> it is only in service of generating a useful test case.  The actual
> compiler testing is 100% dynamic: we run compilers and look for problems.

No, I understand.  It's still always good to run one's code through as stringent a static analysis tool (splint, -Wall and then some, etc) as possible, no?

xoa

--
Andy Lester => andy@petdance.com => www.techworklove.com => AIM:petdance

Follow-Ups:
- Re: [csmith-dev] Fwd: Re: csmith test harness help
  - From: John Regehr <regehr@cs.utah.edu>

References:
- [csmith-dev] Fwd: Re: csmith test harness help
  - From: John Regehr <regehr@cs.utah.edu>

Prev by Date: [csmith-dev] Fwd: Re: csmith test harness help
Next by Date: Re: [csmith-dev] Fwd: Re: csmith test harness help
Previous by thread: [csmith-dev] Fwd: Re: csmith test harness help
Next by thread: Re: [csmith-dev] Fwd: Re: csmith test harness help
Index(es):
- Date
- Thread