[ I sent this before from a different account to that with which I am subscribed. My apologies if it eventually shows up twice. ]
On Mon, Jun 06, 2005 at 11:43:40PM -0500, Trevor and Jenny Williams wrote: > Well, I'm interested in creating a VPI interface for my code coverage > tool, Covered. > > The VPI is quite interesting to me in that I can access more than just > value changes within the design as it is running. Thus, I can get the > information I need (signal, expression and statement information) > without having to do a lot of post-processing of the results. I wrote a code coverage tool using the VPI about six years ago. Unfortunately it was closed source and only targeted ModelSim, but it was pretty easy to write and had a low overhead. Using the VPI it was possible to collect data for all the standard coverage criteria. I still think it is a very sensible solution. Since that time I have written the Perl code coverage module, Devel::Cover. In doing so I made the backend language agnostic so that it could be used to display coverage data from a number of languages and tools. It's primarily used for Perl, of course, but there is also a tool do put gcov data into the database. You can take a look at the sort of output it provides at http://pjcj.sytes.net/cpancover/ If you would like to, you are very welcome to target this as a backend and I would be quite happy to help you do so. Good luck, -- Paul Johnson - [EMAIL PROTECTED] http://www.pjcj.net
