Hi Neil,
Here is SV-AC status summary:
The following issues have been resolved (including proposal amendment addressing the champions feedback):
2093 Checker construct should permit output arguments
3034 Allow continuous and blocking assignments in checkers
3033 Enhance checker modeling capabilities
3213 Update definition of sampled value
2743 Allow subroutine_call_statement in a checker
The champions sent their feedback on the following proposals:
2476 Need clarification about system functions $onehot, etc
3145 Need to clearly define "maximal property"
3564 Sec 9.2.2.2.1 needs to clarify whether variables read in an assertion contribute to the sensitivity of an always_comb
Attached is a list of top priority SV-AC enhancements for this PAR. The enhancements addressed by SV-AC are highlighted.
SV-AC is now working on addressing the champions feedback. The meetings are currently held on an "as need basis".
Dmitry
-----Original Message-----
From: Neil Korpusik [mailto:neil.korpusik@oracle.com]
Sent: Sunday, October 23, 2011 05:00
To: Little Scott-B11206; Korchemny, Dmitry; Maidment, Matthew R; Charlie Dawson; Mehdi Mohtashemi
Cc: Brad Pierce; Thomas Thatcher; Ghassan Khoory; Rich, Dave; Karen Pieper
Subject: P1800 TC status for the Working Group meeting - needed by Wednesday
P1800 technical committee chairs,
The next P1800 working group meeting will be held Thursday (October 27th).
Please provide me with a one page summary of your committee status. We are now at the end of the schedule for this PAR. We will need to have an up-to-date summary for each committee for this meeting.
Please send me a copy of your status by Wednesday afternoon. This will allow me to roll it up into a single document that can be referenced in the minutes.
Neil Korpusik
P1800 Technical Chair
---------------------------------------------------------------------
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.
This archive was generated by hypermail 2.1.8 : Wed Oct 26 2011 - 09:57:12 PDT