[sv-ac] Reminder of SV-AC meeting 2008-04-08

Hi Folks:

 

An agenda is below.  Please let me know if other items should be added.

 

D.K.

 

Meeting reminder for IEEE P1800 SV-AC meeting #2007-49:

 

Date:  2008-04-08

Time:  16:00 UTC (09:00 PDT) 

 

Dialin information:

-------------------

 

Toll number:   +1 916-356-2663

Toll free number (US): 888-875-9370 (U.S. toll-free),

 

Bridge: 4, Passcode: 4055590

 

Agenda:

-------

 

- Reminder of IEEE patent policy.

See: http://standards.ieee.org/board/pat/pat-slideset.ppt

 

New temporal committee to handle checker related proposals.

 

Working items:

 

. 1806 - Introduce "restrict property" verification statement

Waiting for SV-BC and SV-EC feedback.

JB suggest using constraint instead of restrict

 

. 2150 - use of automatic variables in action block and subroutine calls
should not be allowed

 

---------------------------------------------------------------------- 

 Neil Korpusik - 2008-03-08 19:13  

---------------------------------------------------------------------- 

The proposal was unanimously approved by the Champions in the

February 25th, 2008 conference call with friendly amendments.

 

    Friendly amendments:

       - "can only be of a type allowed in 16.5.1" --> "shall be of a

type

          allowed in 16.5.1"

       - "as an argument to subroutine call" --> "as an argument to a

          subroutine call"

       - "associate arrays" --> "associative arrays"

   From:

      The action block of an assert statement shall not refer to an

automatic

      variable, other than a loop control variable, declared outside of

the

      action block.

   TO:

      The action block of an assert statement shall not refer to an

automatic

      variable declared outside of the action block, other than a loop

control

      variable. 

 

---------------------------------------------------------------------- 

 Neil Korpusik - 2008-04-05 18:09  

---------------------------------------------------------------------- 

The proposal was unanimously approved by the Working Group

in the conference call of March 27, 2008. Approval was contingent

upon the changes requested by the champions having been made. 

 

Neil reviewed the set of changes contained in the February 26 version of


the proposal. The changes requested by the Champions have not yet been 

incorporated into the proposal. This proposal can not go to the Approved


state until those changes are made. 

 

 

. 2333 - Champions feedback on 0002173

 

VPI-related items:

 

. 1503 27.33 VPI diagram of propertyinst has no vpiArgument

 

SV-CC feedback:

"27.33 VPI diagram of propertyinst has no vpiArgument. We had thought
that identifiers should have been modeled more like io decls. Jim
suggested we go back to adding a]vpiTypeSpec for prop formal decl and
seq formal decl. Remove the vpiExpr and what it points to with a

dotted enclosure for type spec.  Same thing for seq formal decl. Rest of
the changes seem to be okay.  Abi and Chuck were still not clear on the
proposal.  Jim tried to explain.  Bassam pointed out that there can be
an initialization expression.  Was that what vpiExpr was for? Looks like
we need another proposal before we could accept this one.  Bassam will
try to put together another one for next week."

 

. 2246 VPI definitions of assertkill need modification

New proposal

 

. 2237 VPI additions for 1667

Fix to be consistent with Bassam's changes to 1503.

 

.2336 VPI part of 1757

Reconcile the names in 2336 and 2100 ('On' substr present or absent)
from 2100 and 1757. 2336.  The current 'editors note' is not really
sufficient for this purpose.

 

. 2250 VPI changes related to 1932

Incorporate next->nexttime change from 1732.

 

. 2173, 2326, 2327

Why are these items related to the new committee?

 

Other:

*	Static class variables in assertions. 

 

Opens.

---------------------------------------------------------------------
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.