[sv-ac] feedback to P1800 WG on ballot issue

From: Korchemny, Dmitry <dmitry.korchemny_at_.....>
Date: Mon Apr 20 2009 - 12:10:07 PDT
Hi Neil,

Below is SV-AC effort estimation for ballot issue resolution. Note that the effort estimation should be counted from 2008-04-13.

Thanks,
Dmitry

Effort estimation:
83  - Mantis 2647: Clarification about clock glitches in concurrent assertions – 3wd
84  - Mantis 2656: Clarify difference of $global_clock handling in simulation and formal verification – 2ww (10wd)
88  - Mantis 2658: Default values for untyped formals – 3wd
89  - Mantis 2612: `true should have a backtick in a sequence example – ˝ wd
90  - Mantis 2650: Ambiguity in a sequence repetition [*0] definition – 3wd
91  - Mantis 2652: Future value functions need clarification – 1ww
93  - Mantis 2654: Error in an example of throughout operator – 3wd
95  - Mantis 2659: Backward compatibility issue with sequence property – 1wd
96  - Mantis 2660: Add indices to expressions – ˝ wd
97  - Mantis 2478: Clock flow subclause is not consistent with multiclocked property definition – ˝ wd
98  - Mantis 2661: "Syntax 16-19" is in blue – ˝ wd
99  - Mantis 2541: syntax errors - missing parenthesis – ˝ wd
100 – Mantis 2516: Another contradiction of existing text with 2398 needs to be fixed – ˝ wd

Total:  31 wd (the actual effort estimation may be less since it is possible to work on several items simultaneously).

Specific feedback:

82 – Mantis 2646: Assumption in deferred assertion example should be made explicit
SV-AC recommends to leave the LRM text unchanged since it explicitly mentions the execution in the Active region.

85  - Mantis 2657: Clarify notion of sequence
The word “specifies” is appropriate in the 2nd sentence and it is equivalent to saying “denotes”. The last sentence then refers to the dynamic behavior of SV sequences in terms of the denoted set of linear sequences, namely, when an SV sequence has a match (on a trace containing a finite interval of clock ticks). SV-AC recommends to leave the text unchanged.

86  - Mantis 2648: Need an example of cyclic dependencies between sequences
The example of cyclic dependency between sequences already exists at the bottom of Page 319. SV-AC believes that modifying this example to pass one sequence as an argument to the other will make it less clear. Adding one more example is impractical. Therefore SV-AC recommends to leave the text unchanged.

87  - Mantis 2649: sequence_actual_arg is used to represent the default argument
SV-AC believes that there is no added value in introducing a new non-terminal identical to sequence_actual_arg.  It would also introduce an inconsistency between the BNF of sequences on the one hand, and the BNF of properties, functions, and tasks on the other hand. Therefore SV-AC recommends to leave the text unchanged.

92  - Mantis 2653: Sequence match not shown in timing diagram
SV-AC believes that the figure in question is correct since the text clearly says that Figure 16-5 shows only the evaluation attempt starting at clock tick 8.

94  - Mantis 2655: Backward compatibility issue with the clocking specification
SV-AC requests a clarification on this issue. There is no described backward compatibility issue in Subclause 16.10 Local variables.

139 – Mantis 2496: non_port_program_item should contain assertion_item
16.4.3 “Deferred assertions outside procedural code” states: “A deferred assertion statement may also appear outside procedural code, used as a module_common_item. In such cases, it is treated as if it were contained in an always_comb procedure.” Since an always_comb procedure cannot appear in programs, using deferred assertions in programs should be illegal. Therefore SV-AC recommends to leave the LRM text unchanged.
---------------------------------------------------------------------
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 Apr 20 12:30:29 2009

This archive was generated by hypermail 2.1.8 : Mon Apr 20 2009 - 12:31:33 PDT