around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
Changes since the last stable release:
- User-specified FSM code coverage. By using command-line options or inline code specified
by the user, FSM code coverage can be extracted from the design. This does not include
the ability to automatically extract FSMs from the design (an ability that will be added
in future stable releases).
- Enhanced performance of the score command. A 3x - 5x speedup in the running time of the
score command on the design should be expected with this release over past stable releases.
- Enhanced readability of coverage reports. The coverage report look has been overhauled to
produce a much more readable/understandable coverage report.
- Several bug-fixes have been made, including coverage number calculation bugs.
- Development and user documentation updates.
- Enhanced regression suite.
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.
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.
