[sv-ac] RE: P1800 TC status for the Working Group meeting

Hi Neil,

Since 2010-10-14 the following issues have been resolved:

1627: clarify that expect statement not allowed in functions2206: Random simulation of non-deterministic free variables in checkers
1763: The LRM does not define whether assertion control tasks affect sequence methods and events
2205: $asseroff, $assertkill and $asserton description is ambiguous
2353: 'classes' missing from description
2412: Allow clock inference in sequences
2476: Need clarification about system functions $onehot, etc
2485: terminology related to immediate and deferred assertions
2747: Typing error, missing () around property declaration
2904: Clarify when disable iff condition must occur relative to starting and ending of an attempt
2938: Surprising (to some users) interaction between deferred assertions & short-circuiting
3135: Verbal explanation of nexttime and always is misleading for multiple clocks.

The resolution of the following issues has been rejected by the champions:

1933: reference to triggered method can be improved
2252: Several symbols in Annex F are in green
2291: the description of $assertoff blurs assertions and attempts
2330: Clarify that number_of_ticks argument to $past must be compile-time constant
2387: Layout of 16.11 is inconsistent
2481: Need to swap F.3.4.6 and F.3.4.7
2552: Confusing comments regarding nexttime operator
2557: Rules for passing automatic variables to sequence subroutines are not clear
2722: Errors in Figures 16-14, 16-15, and 16-16
2804: Need to clarify rule (b) in 16.15.6 to allow inferred clock when expression appears in procedural assertion
2839: Contradictory statement of increment/decrement operators usage.
2871: Clause 16 does not forbid assertion local variables within clocking event expressions
2927: Precedence between sequence/property operator and normal expression operator
2934: Precedence and associativity of case operator is not shown in the table
3113: Add port_identifier to constant_primary BNF for sequences, properties and checkers

The resolution of the following issues has been approved:

2494: 37.44 Assertion diagram missing restrict
2558: Restriction inside checker construct
2571: confusing assertion clock inference rule
2732: Clarify timing diagram in Figure 16-4. Future value change

The committee is currently working on the following major errata/enhancements:

2578: Vacuity definition
3034: Allow continuous and blocking assignments in checkers
3206: Deferred assertions are sensitive to glitches
3213: Update definition of sampled value

Regards,
Dmitry

-----Original Message-----
From: Neil Korpusik [mailto:neil.korpusik@oracle.com]
Sent: Saturday, November 06, 2010 3:58 AM
To: Little Scott-B11206; Korchemny, Dmitry; Maidment, Matthew R; Charlie Dawson; Mehdi Mohtashemi
Cc: Brad Pierce; r8aaau@freescale.com; Thomas Thatcher; Ghassan Khoory; Rich, Dave; IEEE P1800 Working Group
Subject: P1800 TC status for the Working Group meeting

P1800 technical committee chairs,

The next P1800 working group meeting will be held next Thursday (Nov 11th).
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. I am
assuming that most committees won't have too much new status since it has
only been 1 month since the Working Group last met.

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.