Next | Query returned 45 messages, browsing 41 to 50 | previous

History of commit frequency

CVS Commit History:


   2004-01-22 08:21:55 by grant beattie | Files touched by this commit (14)
Log message:
replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.
   2003-12-09 02:20:36 by Dan McMahill | Files touched by this commit (2)
Log message:
Update to covered-0.2.2.

>From the NEWS file:

This release is basically a 0.2.1 release with the available bug fixes
patches applied to it.  This should make getting a stable release less
tedious.
   2003-09-02 01:41:37 by Stoned Elipot | Files touched by this commit (1)
Log message:
Fix REPLACE_PERL: pathnames listed should be relative to ${WRKSRC}.
   2003-08-28 05:47:10 by James Chacon | Files touched by this commit (1)
Log message:
Regen with file as sourceforge shows it.
   2003-08-24 20:38:08 by Dan McMahill | Files touched by this commit (5) | Imported package
Log message:
import covered-0.2.1

Covered is a Verilog code coverage analysis tool that can be useful
for determining how well a diagnostic test suite is covering the
design under test. Typically in the design verification work flow, a
design verification engineer will develop a self-checking test suite
to verify design elements/functions specified by a design's
specification document. When the test suite contains all of the tests
required by the design specification, the test writer may be asking
him/herself, "How much logic in the design is actually being
exercised?", "Does my test suite cover all of the logic under test?",
and "Am I done writing tests for the logic?".  When the design
verification gets to this point, it is often useful to get some
metrics for determining logic coverage. This is where a code coverage
utility, such as Covered, is very useful.

Please note that this package is for a stable release version.
There is a seperate package (covered-current) which is made of
development snapshots.


Next | Query returned 45 messages, browsing 41 to 50 | previous