Hi Neil,
Here is the status of SV-AC
The following issues have been resolved:
2839: Contradictory statement of increment/decrement operators usage.
1933: reference to triggered method can be improved
2934: Precedence and associativity of case operator is not shown in the table
2557: Rules for passing automatic variables to sequence subroutines are not clear
3036: Explicitly allow unpacked data types for arguments of assertion system functions
The resolution of the following issues has been approved:
3134: sequence and property range parameters are erroneously defined
2205: $asseroff, $assertkill and $asserton description is ambiguous
2904: Clarify when disable iff condition must occur relative to starting and ending of an attempt
2871: Clause 16 does not forbid assertion local variables within clocking event expressions
2291: the description of $assertoff blurs assertions and attempts
2722: Errors in Figures 16-14, 16-15, and 16-16
2485: terminology related to immediate and deferred assertions
2353: 'classes' missing from description
The following issues have been closed:
1763: The LRM does not define whether assertion control tasks affect sequence methods and events
2206: Random simulation of non-deterministic free variables in checkers
2252: Several symbols in Annex F are in green
3168: expression1 is not an argument to $past
2481: Need to swap F.3.4.6 and F.3.4.7
The committee is working on the following issues:
2476: Need clarification about system functions $onehot, etc
3113: Add port_identifier to constant_primary BNF for sequences, properties and checkers
2328: Review and relax restrictions on data types in assertions
2804: Need to clarify rule (b) in 16.15.6 to allow inferred clock when expression appears in procedural assertion
2412: Allow clock inference in sequences
1627: 17.16: clarify that expect statement not allowed in functions
-----Original Message-----
From: Neil Korpusik [mailto:neil.korpusik@oracle.com]
Sent: Sunday, February 06, 2011 03:40
To: Little Scott-B11206; Korchemny, Dmitry; Maidment, Matthew R; Charlie Dawson; Mehdi Mohtashemi
Cc: 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 (Feb 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 Feb 9 05:05:01 2011
This archive was generated by hypermail 2.1.8 : Wed Feb 09 2011 - 05:05:20 PST