Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verilator coverage testing #178

Open
jbush001 opened this issue Feb 15, 2019 · 1 comment
Open

Verilator coverage testing #178

jbush001 opened this issue Feb 15, 2019 · 1 comment
Labels

Comments

@jbush001
Copy link
Owner

jbush001 commented Feb 15, 2019

Collect coverage information at end of tests.

https://www.veripool.org/projects/verilator/wiki/Manual-verilator

  1. Pass --coverage option to verilator in makefile
  2. Modify c++ test harness to VerilatedCov::write into an output file. There will be one file per test, which should be collected somewhere (this probably needs to be done by test_harness.py)
  3. Run verilator_coverage executable, passing paths of all output files, which it will consolidate.
@jbush001
Copy link
Owner Author

It takes a very long time to compile the full processor model with this enabled, which may be prohibitive. This may still be useful for unit tests.

@jbush001 jbush001 added the test label Mar 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant