RE: [sv-ec] Conflicting name creation for coverpoints

I think I asked this question already.

The answer I got was that this is covered by the following test in 19.5:

"A coverpoint name has limited visibility. An identifier can only refer to a coverpoint in the following contexts:
- In the coverpoint list of a cross declaration (see 19.6),
- In a hierarchical name where the prefix specifies the name of a covergroup variable. For example, cov1.cp.option.weight where cov1 is the name of a covergroup variable and cp is the name of a coverpoint declared within the covergroup.
- Following ::, where the left operand of the scope resolution operator refers to a covergroup. For example, covtype :: cp :: type_option.weight." 

and this in 19.3:

"The formal arguments of a covergroup cannot be accessed using a hierarchical name (the formals cannot be accessed outside the covergroup declaration)."

Thus, in the contexts listed in 19.5, the coverpoint name is referred to. In all other contexts, the argument name is referred to.

I don't like it either, but was overruled.

This was Mantis 1279.

Shalom


> -----Original Message-----
> From: owner-sv-ec@server.eda.org 
> [mailto:owner-sv-ec@server.eda.org] On Behalf Of Saurabh Sharma
> Sent: Monday, October 26, 2009 11:39 AM
> To: sv-ec@eda.org
> Subject: [sv-ec] Conflicting name creation for coverpoints
> 
> Hi All,
> 
> I have a query regarding naming for coverpoints when 
> covergroups have arguments.
> 
> Consider the following definition of a covergroup:
> 
> covergroup cg(ref logic [23:0] f1) @(posedge clk);
>   coverpoint f1 {
>       bins b1[] = {[0:20]};
>   }
> endgroup
> 
> As per section 19.5 of draft 9 of SysV LRM "If the label is 
> omitted and the coverage point is associated with a single 
> variable, then the variable name becomes the name of the 
> coverage point." This is shown in one example as well.
> 
> But here this causes conflict as we will have a coverpoint 
> with the name "f1"
> as well as an reference parameter with the same name "f1". 
> Now both these symbols
> having same name "f1" exist in the same scope i.e. covergroup 
> scope. Isn't this ambiguous?
> 
> Thanks
> Saurabh
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


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