[sv-ec] RE: Resending : Clarification or Expedited resolution of Mantis ID 3657

Anupam,

I don't believe there is a contradiction. The statement in 19.5.7 is referring only to an range specification, hence, the warning is only required when the expression has X/Z bits in a range where it is ambiguous how to compute range/membership with expressions involving X/Z, but not in a singleton value, which uses === . This was introduced in Mantis 1313 - http://www.eda.org/svdb/view.php?id=1313.

                Arturo

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Anupam Singal
Sent: Thursday, February 28, 2013 5:06 AM
To: sv-ec@eda.org
Cc: Devraj Goyal
Subject: [sv-ec] Resending : Clarification or Expedited resolution of Mantis ID 3657



There seems to be a conflict in the section 19.5.4 section ( Wildcard specification of coverage point bins)
and section 19.5.7 (Value resolution )  for a particular case of NON wild card bin having X or Z .


eg   for   bin[]=   { 4'b10XZ  }  ;

Q )     Should one check explicitly for X and Z using === operator as per  section 19.5.4

OR

   Issue a Warning as per section 19.5.7  Value resolution, sub-section b 3) as below


" ...
3) If b yields a value with any x or z bits.

This rule does not apply to wildcard bins because x
and z shall be treated as 0 and 1 as described above.
... "

The same had been captured earlier in Ref Mantis ID 3657 and is awaiting comments / resolution .

Could  someone clarify the above case above by way of comments /  clarification or expedite the resolution on this ID ?


Regards ,
Anupam Singal
sanupam@cadence.com<mailto:sanupam@cadence.com>





--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.