Re: [sv-ec] Mantis 2149 - Covergroups sample method with arguments

From: Michael Burns <michael.burns_at_.....>
Date: Wed Nov 14 2007 - 11:59:07 PST

Hi folks,

I only have one comment (marked with "MJB:")...

Mike Burns

David Scott wrote:
A few responses marked with "DCS:" ... no response means in general I concur.

-- David (Scott)

Arturo Salz wrote:

Scott,

 

My comments inlined below.

 

            Arturo

 


From: David Scott [mailto:david_scott@mentor.com]
Sent: Friday, November 09, 2007 2:27 PM
To: Arturo Salz
Cc: SV-EC; sv-ac@eda-stds.org
Subject: Re: [sv-ec] Mantis 2149 - Covergroups sample method with arguments

 

Arturo:

snip...

 

#6.  A host of issues around sample arguments.  One thing that occurred to us -- without, I'll note, Gordon's blessing! -- is that we could possibly allow this:

int a;
covergroup ct function sample(ref int x = a);
    coverpoint a;

This would allow event-based sampling to occur as well as procedural sampling, let's say with this syntax (which I know would be a change from the proposal):

covergroup ct function sample(ref int x = a) @(e);

With event-based sampling, the default arguments would be used, which as you see cause "a" from the enclosing scope to be sampled.  It wasn't clear from Mike's original e-mail whether the override was expected to be optional (used occasionally) or required (used always).

I am very uncomfortable with this change. The current proposal makes it clear that there are two mutually exclusive ways to trigger a covergroup: via an events (or block event) or procedurally through the sample method. Otherwise, there are other issues like “strobe” sampling that rear their ugly head.


DCS: I'm OK disallowing what I suggested; it does make it simpler to disallow it.  I'll comment on "strobe" later in the thread, though
MJB: Freescale's intention was not to mix the two types of triggering; I don't see that it would be useful to us. If someone strongly wants this feature I won't object, but I'd much rather keep it simple and easily passable.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. Received on Wed Nov 14 11:59:36 2007

This archive was generated by hypermail 2.1.8 : Wed Nov 14 2007 - 11:59:44 PST