Re: [sv-ec] Ballot issue #106

From: David Scott <david_scott_at_.....>
Date: Fri Apr 24 2009 - 09:29:23 PDT

Well, again, I think the instructions from P1800 are to work on ballot issues only.  Neil can confirm.

I don't think the first point is very unclear.  Look for the phrase "will not track" in the paragraph about covergroup arguments.

The second case may actually be unclear (I started off writing that it wasn't.)  The visibility of the arguments should follow the same rules as resolving arguments in any other scope.  However, the coverpoint is a sub-scope of the covergroup scope, so the bin name should arguably hide (or override) the name in the higher scope.  On the other hand, bin names really aren't visible in the language, except in cross select expressions, so maybe they don't.  Yes, this should probably be clarified, but it is not a ballot issue against 1800-2009.

Dave



Swapnajit Chakraborti wrote:

Hi Dave,

 

Did you get a chance to look at the two points that I raised alongwith #106? These were not part of the

ballot, but were posted to the reflector as comments. I am mentioning them once again for your reference.

 

- Use of "input" type arguments as part of coverpoint expressions. I do not see an

  issue with this but just wanted to clarify as LRM is silent on this. LRM just shows

  "ref" arguments being used as coverpoint expressions.

- Use of covergroup arguments as bin name. Probably we should mention in LRM

  that this should be an error. An example of this is given below:

  covergroup cg (int f1,..)@..

     coverpoint a {

        bins f1 = {..};  // Note "f1" is used as bin name

     }

  endgroup

 

Regds,

Swapnajit

---

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Scott, David
Sent: Thursday, April 23, 2009 3:56 AM
To: sv-ec@eda.org
Subject: [sv-ec] Ballot issue #106

This is the one about covergroup arguments using "output" ...

 

http://www.eda-stds.org/mantis/view.php?id=2710

 

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

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. Received on Fri Apr 24 09:35:39 2009