SV-EC Committee Meeting. Monday November 20 2006 11:00am - 1:00pm PST [Minutes distributed for review, to be approved at next meeting] (12120202) Day (48159360) (00001111) Month (88990011) (00000000) Year (66666666) --------- Attendees ---------- (-AAAAAAA) Arturo Salz (--AAA-AA) Cliff Cummings (AAAAAAA-) Dave Rich (AA-A-AAA) Francoise Martinolle (-AAAAAAA) Mehdi Mohtashemi (AAAAAAAA) Neil Korpusik (AAAAAAAA) Ray Ryan (AAAAAAAA) Gordon Vreugdenhil (AAAAAA--) Steven Sharp (--AAAA-A) Phil Moorby (---AA-AA) Doug Warmke (AAAAAAA-) Stu Sutherland (-AAAA--A) Heath Chambers (-AAAAAA-) Don Mills (--AA--A-) Jonathan Bromley (--A-----) Logie Ramachandran (----AAAA) Melvin Cardoza (-----A-A) Mark Hartoog (-------A) Satia (from Intel) ^ |------- non-voting meeting ** Minutes taken by Neil Korpusik and Mehdi Mohtashemi Neil chaired the meeting while Mehdi was on mute. ////////////////// Nov 20, 2006 ///////////////////////// Agenda: 1. IEEE patent policy ref: http://standards.ieee.org/board/pat/pat-slideset.ppt Move: Cliff - Assume that the patent policy was read Second: Heath Abstain: none Opposed: none passed 2. Review meeting minutes/Notes: a) Review meeting minutes of October 23rd 2006 This set of minutes was not yet ready for review. b) Review/discuss notes of face-to-face meeting November 6th 2006 www.eda-stds.org/sv-ec/Minutes/SV-EC_f2f_Meeting_November_6_2006_Notes.txt Move: Doug - Approve minutes Second: Cliff Abstain: none Opposed: none passed c) P1800 meeting (November 9th) summary - Stu has been selected to be the editor. The first activity for him will be to update the LRM with the 200 mantis items that have been approved by the P1800 - ECD Jan 15, 2007. The merged LRM is expected by Mar 07, 2007. - The SVEC will have until July 1, 2007 to finish up with errata. The committee should provide feedback if this deadline will be a problem. - New officers Karen - Chair Neil - Co-Chair Dennis - Secretary - Verilog-AMS will be a "dot" standard - A new technical committee will be formed - SVXC It will handle cross-language issues. VHDL interoperability will be part of their initial focus. 3. Action items review --------------------------- November 6 2006: Doug - rewrite the proposal for mantis 890 based on our agreements There was no work on this yet. Doug was looking for feedback on the results of the face-to-face meeting before spending a lot of time on the new proposal. - Jonathan - might be interested in helping? - Doug plans to update the "Arturo #4 proposal". - Doug wants the new proposal to be non-verbose but complete. - Doug would like Cliff and Jonathan to review the new proposal. ? - rewrite the description of #1step in 17.3 AI/Arturo & Cliff - will work on the event scheduling portion. AI/Doug - rewrite the description of #1step in 17.3 (shouldn't be too tough) AI/Mehdi - talk to svac about the change to #1step, review before we vote. Action items: Previous meetings AI: follow-up to mantis 978 Neil - rewrite unique(), the first 2 sentences appear to be contradictory. - Make sure that it is clear that array elements are returned. - Add some examples for unique(). ** This will be tracked as mantis 1576 Neil - Array reduction methods can operate on arrays of non-integral values when a with clause is specified, as long as the type of the expression is an integral value. ** A new mantis item will be opened for tracking this. Gord - re-write section 5.15.4 - only the default argument value makes sense. Dave - what order is used for find and find_index (e.g. traversal is left to right of the bounds, associative is min to max) - 5.15.1 - change last sentence in first paragraph. All - can anyone come up with a realistic example? (last example 5.15.4) - not only where you would need it but also what does it mean. 4. Name Resolution sub-group update ------------------------------------ Gord wasn't yet on the call when we got to this item. 5. Discussion on the face-to-face meeting and its related mantis items: -------------------------------------- Item 4) Areas of general agreement Move: Doug - Close mantis 1604 since it is covered by mantis 890 Second: Cliff Abstain: none Opposed: none passed Cliff - Would like Steven Sharp to review the minutes. FM - Item 4.f) of the minutes could cause some problems. (Steven) - Can't generate code for the task since it could execute in either region. Gord - needs to be aware of where being called. - there are multiple ways of implementing this. - thinks there are efficient ways to implement this. Doug - Thought that Steven was ok with 4.f) - This was in the Mentor ballot comments. Cliff - 4.f) simplified things a lot 4.e) and 4.f) were the biggest decisions from the F2F. Fm - backward compatible? Arturo - It changes cases that were indeterminable. - They are currently ambiguous. Cliff - Expects most code to continue to work. Arturo - Views it as a change, not an enhancement. Cliff - Was pleased with the set of agreements from the F2F. Heath - now ok with ##1 (originally had issues with it -- ok with the new clarifications) Cliff notes - See the bottom portion of the minutes from the F2F. We reviewed these. 1. cb port assignments Gord - Thought there might still be one area of ambiguity here. - What contribution does a clocking drive make to a net when a clocking drive is not active? If the only contributor, does the net float to z, or does last driven value appear on the net? Arturo - It depends on final destination. Gord - For a net -- Arturo - last driven value should remain. Cliff - multiple clocking drive (depends on whether driven from same cb) Gord - will use net-value resolution (not cb resolution). - non-net type output - output of cb only when clocking drive is active? Cliff - logic a; a = 0; // from program block (at time 0) ##3 cb1.a = 1; Gord - when clocking event happens is value driven to reg only when it occurs or always driven out? - only driven when active -- his assumption 2. port collapsing Cliff - Facilitated because of thread-based approach. 3. Are program variable ports considered program variables? Cliff - ref ports cause problems. Arturo - calling a task from program or module - resolved now - by the thread-based approach. The call determines the scheduling. 4. port connections - design ports versus program ports 5. program calling a blocking task from a module Cliff - now all execute in reactive loop. 6. continuous NBA - deferred to later 7. re-NBA region 8. 9. NBA to program variables --------------------- Gord - we would like to know about any serious objections early. - all of the corner cases were dealt with by agreeing to some key points. If we have to reopen them we need to have another big discussion. - scheduling portion should be quite easy. Cliff - will put together some examples for 890. - 3-4 examples - with hope to add to 890 Doug - the examples need to be fairly short ones. Neil - There should only be a need to have one complete one. AI/FM - try to get Steven to give us feedback soon. b) 890 08-31-06 clarifications in program and clocking blocks (Doug) additional mantis items Additional mantis items 236 - should be resolved... ##0 239 - will close it 597 - AC ; close this one 608 - being clarified. 609 - association of clocking block, need a syntactic form. 1325 - was closed by SVAC - unnamed clocking blocks 1615 - was approved already - allows fork/join_none within functions 564 - Cross-program variable access (Sharp) [recommendation: to close] 553 - Program block exit semantics (Sharp) 551 - Program block interaction with queues (Sharp) 6. Review other mantis item list. ---------------------------------------- 1623 - Heath will provide a proposal - timeunit and timeprecision 7. Next meetings December 4 2006 8. Mantis was down We were unable to continue to make progress since Mantis was down. Move: Cliff - to adjourn Second: Heath ========== ADDITION TO the minutes, not part of regular ========= ========== meeting discussions, informational purposes ========= ========== Action Items updated based on November 20 2006 ==== Action items: November 20, 2006 ------------------------- AI: 890 Arturo, Cliff : will work on the event scheduling portion. Doug : rewrite the description of #1step in 17.3 (shouldn't be too tough) Mehdi : talk to svac about the change to #1step, review before we vote. Francoise: Have steven give the committee feedback soon. AI: 1623, Heath: provide a proposal - timeunit and timeprecision.