RE: [sv-ec] Covergroup declaration

Hi,

In the ballot draft, 9.3.4 describes Block Names, and says,

"A matching block name may be specified after the block end, join, join_any, or join_none keyword,
preceded by a colon. This can help document which end or join, join_any, or join_none is associated
with which begin or fork when there are nested blocks. A name at the end of the block is not required. It
shall be an error if the name at the end is different from the block name at the beginning." 

Regards,
Shalom


> -----Original Message-----
> From: owner-sv-ec@server.eda.org 
> [mailto:owner-sv-ec@server.eda.org] On Behalf Of Neil Korpusik
> Sent: Thursday, August 06, 2009 4:33 AM
> To: SV_EC List
> Cc: devrajg@cadence.com
> Subject: [sv-ec] Covergroup declaration
> 
> <forwarding email from non-member devrajg@cadence.com>
> 
> -------- Original Message --------
> Date: Wed, 5 Aug 2009 10:05:51 +0530
> From: Devraj Goyal <devrajg@cadence.com>
> To: <sv-ec@server.eda.org>
> Subject: Covergroup declaration
> 
> 
> Hi,
> 
> As per LRM BNF of covergroup declaration is :
> 
> covergroup_declaration ::=
>          covergroup covergroup_identifier ;
>               ...........
>          endgroup [ : covergroup_identifier ]
> 
> I do not find anything in LRM if covergroup_identifier used in
> covergroup declaration, and in label must be same or not.
> 
> Example
> 
> covergroup cg_name1;
>     ......
> endgroup:cg_name2                // should this be allowed?
> 
> In the example covergroup is declared with cg_name1 and labeled with
> cg_name2.
> 
> Please let us know what should be the behavior in this case.
> 
> Thanks,
> Devraj
---------------------------------------------------------------------
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.