[sv-ac] SV-AC meeting minutes, 2009-04-13

From: Korchemny, Dmitry <dmitry.korchemny_at_.....>
Date: Mon Apr 13 2009 - 12:47:54 PDT
Minutes of IEEE P1800 SV-AC meeting #2009-01



Date:  2009-04-13

Time:  16:00 UTC (09:00 PDT)



Dialin information:

-------------------

Toll number:   +1 916-356-2663

Toll free number (US): 888-875-9370 (U.S. toll-free),

Bridge: 2 Passcode: 3954324


Attendance Record:
------------------
        Legend:
               x = attended
               - = missed
               r = represented
               . = not yet a member
               v = valid voter (2 out of last 3)
               n = not a valid voter
               t = chair eligible to vote only to make or break a tie

Attendance re-initialized on 2009-04-13:

vv[x] Doron Bustan (Intel)
vv[x] Eduard Cerny (Synopsys)
vv[x] Ben Cohen
vv[x] John Havlicek (Freescale)
vv[x] Tapan Kapoor (Cadence)
tt[x] Dmitry Korchemny (Intel - Chair)
vv[x] Manisha Kulshrestha (Mentor Graphics)
vv[x] Erik Seligman (Intel)
vv[x] Bassam Tabbara (Synopsys)
vv[x] Tom Thatcher (Sun Microsystems – Co-Chair)
   |-------------- attendance on 2009-04-13
 |---------------- voting eligibility on 2009-04-123
|----------------- new voting eligibility






Agenda:

-------



- Reminder of IEEE patent policy.

See: http://standards.ieee.org/board/pat/pat-slideset.ppt



- Review of ballot issues.

  The Ballot Comments from the March 2009 P1800 Ballot can be found at:



  http://www.eda-twiki.org/cgi-bin/view.cgi/P1800/P1800BallotReviewFeedback



  The goal is to look over the ballot feedback for SV-AC,

  and report back to the P1800 by 4/16 as to how long SV-AC

  thinks they require to address the feedback.

  The current target  is May 14, 2009.





Ballot issue discussion and effort estimation:



82 – Mantis 2646: Assumption in deferred assertion example should be made explicit



There is no need to make changes in the LRM text since the text explicitly mentions the execution in the Active region.



Ed moves.

Erik seconds.



Motion passed 9y/0a/0n.





83  - Mantis 2647: Clarification about clock glitches in concurrent assertions



Ed: Add a clarification that the tool is not required to check the clock glitches.

Effort estimation: 3 days.





84  - Mantis 2656: Clarify difference of $global_clock handling in simulation and formal verification



Ed: Provide an example with multiple clocks

Effort estimation: 2 weeks





85  - Mantis 2657: Clarify notion of sequence



Ed: 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).



Doron: Leave the text unchanged.

John seconds.



Motion passed 9y/0a/0n.





86  - Mantis 2648: Need an example of cyclic dependencies between sequences



As Shalom mentioned there already is an example of cyclic dependence between sequences on page 319.



John: It is easy to change the example to pass one sequence as an argument to the other.

Dmitry: But the intent will be less clear.

John: Leave the text unchanged.

Ed seconds.



Motion passed 9y/0a/0n.





87  - Mantis 2649: sequence_actual_arg is used to represent the default argument



Ed: There is no added value in introducing a new non-terminal identical to sequence_actual_arg.

John: The current BNF is consistent with that one for functions and tasks.

John: Leave the text unchanged.

Doron seconds



Motion passed 9y/0a/0n.





88  - Mantis 2658: Default values for untyped formals



Ed: The LRM does not disallow it.



Effort estimation: 3 days.





89  - Mantis 2612: `true should have a backtick in a sequence example



Trivial editorial issue.



Effort estimation: ˝ day.





90  - Mantis 2650: Ambiguity in a sequence repetition [*0] definition



John, Ed, Dmitry: The text is correct. Probably some minor clarification is needed.



We didn’t have time to elaborate a resolution, the discussion is postponed to the next meeting.





91  - Mantis 2652: Future value functions need clarification



Discussion postponed to the next meeting.





92  - Mantis 2653: Sequence match not shown in timing diagram



Discussion postponed to the next meeting.





93  - Mantis 2654: Error in an example of throughout operator



Discussion postponed to the next meeting.





94  - Mantis 2655: Backward compatibility issue with the clocking specification



Dmitry: The intent is not clear, there is no backward compatibility issue in the specified subclause (16.10 Local variables).

Tapan: The system function $sampled is intended.

Dmitry: The deprecation message appears in C.2.2.

Doron: Leave the text unchanged.

John seconds.



Motion passed 9y/0a/0n.





95  - Mantis 2659: Backward compatibility issue with sequence property.



Doron: Add a note about the lack of backward compatibility.



Effort estimation: 1 day.





96  - Mantis 2660: Add indices to expressions



Discussion postponed to the next meeting.





97  - Mantis 2478: Clock flow subclause is not consistent with multiclocked property definition



Effort estimation: ˝ day.





98  - Mantis 2661: "Syntax 16-19" is in blue.



Discussion postponed to the next meeting.





99  - Mantis 2541: syntax errors - missing parenthesis



Effort estimation: ˝ day.





100 – Mantis 2516: Another contradiction of existing text with 2398 needs to be fixed



Effort estimation: ˝ day.





139 – Mantis 2496: non_port_program_item should contain assertion_item



Effort estimation: ˝ day.



- Opens.



Next meeting will take place 2009-04-16 16:00 UTC (09:00 PDT)

---------------------------------------------------------------------
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 13 12:49:02 2009

This archive was generated by hypermail 2.1.8 : Mon Apr 13 2009 - 12:50:04 PDT