[sv-ec] Re: Updated version of 2506 (covergroup filtering)

Hi Scott,
We can start with 2506 next meeting,
Regards,
Mehdi

----- Original Message -----
From: Little Scott-B11206 [mailto:B11206@freescale.com]
Sent: Tuesday, April 19, 2011 06:46 PM
To: sv-ec@eda.org <sv-ec@eda.org>
Cc: Fais Yaniv-RM96496 <RM96496@freescale.com>; Michael Burns <michael.burns@oracle.com>; Mehdi Mohtashemi <Mehdi.Mohtashemi@synopsys.COM>
Subject: Updated version of 2506 (covergroup filtering)

Hi all:

I have uploaded a revised version of the proposal for mantis 2506. The major changes are described below. I don't want to be too presumptive, but if it is okay with Mehdi I would like to suggest that we discuss this proposal first in the SV-EC meeting on 04-25. I hope that will give interested parties enough time to review the proposal and arrange their schedules to attend the meeting. Mehdi, are you okay with that?

Thanks,
Scott

mantis link: http://www.eda.org/svdb/view.php?id=2506
.docx link: http://www.eda.org/svdb/file_download.php?file_id=4928&type=bug

Major changes for v3
-Removal of <> syntax to enclose set_expression to syntax 9-2 and removed from affected examples.
-Added restriction that identifiers in the with expressions, set expressions, and cross functions are limited to constant expressions, instance constants (for classes only), or non-ref arguments to the covergroup. This is consistent with previous restrictions to variables in the open_range_list.
QUESTION: I don't like repeating the restriction several times. I wouldn't mind referencing the restriction, but it seems silly to create a subsection for a sentence just because it is used often. Does someone else have an idea to enable me to write the restriction once and use it many times?
-Added a restriction in Section 19.5.1.1 that disallows non-pure user-defined systfs
-Specified with_expression application prior to bin distribution as the default behavior
-Added distribute_first covergroup option to cause bin distribution to happen prior to with_expression application
-Removed text describing how to access the cross types from outside the cross scope.
-Added a restriction that the cross types are only accessible from within the cross scope.

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