[sv-ec] RE: Mantis 2506 BNF for coverpoint

It's not consistent with p1800's typed variable syntax. If we are to treat coverpoints as typed variables, let's be consistent.

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Little, Scott
Sent: Friday, January 27, 2012 10:53 AM
To: Rich, Dave; sv-ec@eda.org
Subject: [sv-ec] RE: Mantis 2506 BNF for coverpoint

Hi Dave,

Thanks. This point has been raised to me as well as a couple of other fixes that are needed.

I would prefer to adjust the BNF to be consistent with the example as I believe that is a more intuitive way to write it. Do you foresee any issues with that BNF change?

cover_point ::= // from A.2.11
              [ cover_point_identifier : ] data_type_or_implicit coverpoint expression [ iff ( expression ) ]

Thanks,
Scott

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Rich, Dave
Sent: Friday, January 27, 2012 8:48 AM
To: sv-ec@eda.org
Subject: [sv-ec] Mantis 2506 BNF for coverpoint

While I've got your attention for mantis 2506,

The BNF for a coverpoint says

cover_point ::= // from A.2.11
              data_type_or_implicit [ cover_point_identifier : ] coverpoint expression [ iff ( expression ) ]

Yet a later example has

d: bit [7:0] coverpoint y[31:24]; // creates coverpoint "d" covering ...

Which is correct?

Dave Rich
Verification Technologist
Mentor Graphics Corporation
[Description: Description: Twitter-32]<http://www.twitter.com/dave_59>[Description: Description: Technorati-32]<http://go.mentor.com/drich>

--
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<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.