SV-AC status
The following issues have been resolved:
1756: The LRM does not indicate how the control tasks $asserton/off/kill affect verification statements in initial blocks
2386: Rename 16.9 to "Local variables"?
2412: Allow clock inference in sequences
2557: Rules for passing automatic variables to sequence subroutines are not clear
2839: Contradictory statement of increment/decrement operators usage.
3036: Explicitly allow unpacked data types for arguments of assertion system functions
3113: Add port_identifier to constant_primary BNF for sequences, properties and checkers
3135: Verbal explanation of nexttime and always is misleading for multiple clocks.
3376: triggered should be typeset as code
The following issues have been approved by P1800 WG
2330: Clarify that number_of_ticks argument to $past must be compile-time constant
2452: No vacuity information about synchronous aborts
2552: Confusing comments regarding nexttime operator
2927: Precedence between sequence/property operator and normal expression operator
2938: Surprising (to some users) interaction between deferred assertions & short-circuiting
2934: Precedence and associativity of case operator is not shown in the table
The committee is working on the following issues:
2476: Need clarification about system functions $onehot, etc
2804: Need to clarify rule (b) in 16.15.6 to allow inferred clock when expression appears in procedural assertion
3069: Relax rules for $global_clock resolution
3191: Allow sequence methods with sequence expressions
3295: need a way to control only asserts/covers/assume directives
The committee held a F2F meeting 3-4-Mar-2011. The main outcome of the meeting was solution elaboration for checker enhancements and other major features from the SV-AC to-do list and issue prioritization.
Regards,
Dmitry
-----Original Message-----
From: Neil Korpusik [mailto:neil.korpusik@oracle.com]
Sent: Sunday, March 06, 2011 06:24
To: Little Scott-B11206; Korchemny, Dmitry; Maidment, Matthew R; Charlie Dawson; Mehdi Mohtashemi
Cc: Jim.Lear@cirrus.com; Brad Pierce; Thomas Thatcher; Ghassan Khoory; Rich, Dave
Subject: P1800 TC status for the Working Group meeting
P1800 technical committee chairs,
The next P1800 working group meeting will be held next Thursday (March 10th).
Please provide me with a one page summary of your committee status.
Don't worry too much about format. It is the content that is important. If you
have any requests that need to be made to the Working Group, they should be
listed in your summary. For those that provide word files, I will most likely
copy them directly into the final writeup. That process has been working fairly
well in the past and I will continue to do that.
Please send me a copy of your status by Wednesday morning. 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.Received on Wed Mar 9 00:08:01 2011
This archive was generated by hypermail 2.1.8 : Wed Mar 09 2011 - 00:08:21 PST