[sv-ec] RE: Clarification needed regarding covergroup option cross_num_print_missing definition

From: Vaibhav Bhutani <vbhutani@cadence.com>
Date: Wed Nov 10 2010 - 03:56:45 PST

Gentle Reminder!
Any help or feedback regarding this will be valuable to us.

Regds
Vaibhav Bhutani

From: Vaibhav Bhutani
Sent: Monday, November 08, 2010 11:01 AM
To: sv-ec@eda.org
Cc: Vaibhav Bhutani
Subject: Clarification needed regarding covergroup option cross_num_print_missing definition

Hi,

We have some queries regarding covergroup option cross_num_print_missing.

As per LRM, this option is defined as follows:

"Number of missing (not covered) cross product bins that shall be saved to the coverage database and printed in the coverage report."

This definition raises certain questions which are as follows:

1. Does the word "saved" mean that number of uncovered cross bins that are dumped to coverage database is equal to cross_num_print_missing

   and rest of the uncovered cross products bins are not dumped to coverage database and thus removed from coverage space and

   coverage calculation?

2. What is the real intent of this feature: to make the report more readable by removing "unwanted content" from printing or

   to help reduce the coverage space/database size as well?

If we go by exact wording in LRM definition, and remove the other uncovered cross bins from database and from the coverage space, then the final coverage value may be of no use, and this may also impact the analysis of coverage model.

Secondly, if the intent is only to make the report more readable then all uncovered cross bins can still be saved to coverage database and can be used in computation of coverage. But user can see a more readable report as well.

Please help us in building the understanding about how the LRM definition should be interpreted.

Vaibhav Bhutani | SMTS, Incisive Comprehensive Coverage, Functional Verification | Cadence

P: 91.120.3984000 M: 91.9899811123 F: 91.120.3984203 www.cadence.com<http://www.cadence.com>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Wed Nov 10 03:57:14 2010

This archive was generated by hypermail 2.1.8 : Wed Nov 10 2010 - 03:57:37 PST