Hi all,
Below is the list of resolved Mantis items for your information that Ed collected from SV-AC status reports.
Thanks,
Dmitry
11/9:
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
12/8:
The following issues have been re-resolved following the champions' feedback:
1933: 16.13.6 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
2552: Confusing comments regarding nexttime operator
2722: Errors in Figures 16-14, 16-15, and 16-16
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
3168: expression1 is not an argument to $past
The committee is still discussing potential introduction of continuous assignments in checkers. Several directions that we considered have serious drawbacks and we are looking for an acceptable definition.
1/12:
The following issues have been resolved:
2387: Layout of 16.11 is inconsistent
2934: Precedence and associativity of case operator is not shown in the table
We are working on the following planned enhancements:
3036: Explicitly allow unpacked data types for arguments of assertion system functions
3037: Introduce assertion system functions for 4-valued type support
We would like to request authorization to work on the following enhancement:
3295: need a way to control only asserts/covers/assume directives
SV-AC is planning to hold a F2F meeting in the beginning of March.
2/9:
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
3/9:
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.
5/11:
The following issues have been resolved:
1675 Assertion system function syntax is not complete
2209 Add optional event control to deferred assertions in 2005
2271 sequence events require a clocked sequence2387 Layout of 16.11 is inconsistent
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
3037 Introduce assertion system functions for 4-valued type support
3191 Allow sequence methods with sequence expressions
3377 Fix method names in C.2.3 ended sequence method
3491 Incorrect local variable flow rule in F.5.4
The committee is working on the following enhancements:
3069: Relax rules for $global_clock resolution
3213: Update definition of sampled value
3295: need a way to control only asserts/covers/assume directives
3385: Possible ambiguity when deferred assertion action block calls nested function
The committee is also working on P1800-11-1 Draft review.
6/15:
The following issues have been resolved:
2271 sequence events require a clocked sequence
2556 Explicit package scope indication is not allowed for checkers
3213 Update definition of sampled value
3295 need a way to control only asserts/covers/assume directives
3491 Incorrect local variable flow rule in F.5.4
The following issues have been reviewed by the champions and sent back to SV-AC with comments to be addressed:
2412 Allow clock inference in sequences
2476 Need clarification about system functions $onehot, etc
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.
3385 Possible ambiguity when deferred assertion action block calls nested function
The committee is now working on checker usability enhancements:
3033 Allow procedural control statements is checkers
3034 Allow continuous and blocking assignments in checkers
3035 More flexible definition of checker argument sampling
7/12:
The following issues have been resolved:
1646 Generate constructs within properties and sequences
2412 Allow clock inference in sequences
3069 Relax rules for $global_clock resolution
The following issues have been sent back from the champions:
2476 Need clarification about system functions $onehot, etc
3385 Possible ambiguity when deferred assertion action block calls nested function
The following issue has been set into Feedback status by SV-AC to address Shalom's comments:
3295 need a way to control only asserts/covers/assume directives
SV-AC is working on addressing the champions' feedback and on checker usability enhancements (Mantis 3033).
7/13:
The following issues have been resolved:
1646 Generate constructs within properties and sequences
2412 Allow clock inference in sequences
3069 Relax rules for $global_clock resolution
3385 Possible ambiguity when deferred assertion action block calls nested function
The following issues have been sent back from the champions (not amended yet):
2476 Need clarification about system functions $onehot, etc.
The following issue has been set into Feedback status by SV-AC to address Shalom's comments:
3295 need a way to control only asserts/covers/assume directives
SV-AC is working on addressing the champions' feedback and on checker usability enhancements (Mantis 3033).
8/10:
3135 Verbal explanation of nexttime and always is misleading for multiple clocks.
3202 Clarify on whether certain system functions are allowed in classes, 'let', and other corner cases
3213 Update definition of sampled value
The following issues have been sent back from the champions (not amended yet):
2476 Need clarification about system functions $onehot, etc
3015 Examples of $fatal have bad arguments
3069 Relax rules for $global_clock resolution
3113 Add port_identifier to constant_primary BNF for sequences, properties and checkers
3385 Possible ambiguity when deferred assertion action block calls nested function
SV-AC is working on reviewing Draft 2, addressing the champions' feedback and on the following enhancements:
2328 Review and relax restrictions on data types in assertions
3033 Allow procedural control statements is checkers
3206 Deferred assertions are sensitive to glitches
9/6:
2328 Review and relax restrictions on data types in assertions
2476 Need clarification about system functions $onehot, etc
2547 local variable read before write
2578 Vacuity definition
2743 Allow subroutine_call_statement in a checker
2809 Checker instantiation in checkers' always procedure
2897 Allow $display in checkers
3015 Examples of $fatal have bad arguments
3069 Relax rules for $global_clock resolution
3033 Allow procedural control statements is checkers
3034 Allow continuous and blocking assignments in checkers
3113 Add port_identifier to constant_primary BNF for sequences, properties and checkers
3206 Deferred assertions are sensitive to glitches
3295 need a way to control only asserts/covers/assume directives
3385 Possible ambiguity when deferred assertion action block calls nested function
The following issues has been sent to SV-BC, SV-CC, and SV-EC for backward compatibility review per the champions request. No feedback received yet:
3069 Relax rules for $global_clock resolution
SV-AC is completed reviewing Draft 2. All issues have been reported to the editor.
SV-AC is currently working on Mantis 2093: Checker construct should permit output arguments. This is the last enhancement SV-AC is planning to implement at this PAR.
SV-AC expects significant amount of work in addressing the champions feedback on the recently implemented major enhancements.
---------------------------------------------------------------------
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 Mon Oct 3 11:58:03 2011
This archive was generated by hypermail 2.1.8 : Mon Oct 03 2011 - 11:58:09 PDT