SV-EC Committee Meeting. Monday January 08 2007 11:00am - 1:00pm PST [Minutes distributed for review, to be approved at next meeting] (12120202010) Day (48159360488) (00001111110) Month (88990011221) (00000000000) Year (66666666667) --------- Attendees ---------- (-AAAAAAAAAA) Arturo Salz (--AAA-AAAAA) Cliff Cummings (AAAAAAA-AAA) Dave Rich (AA-A-AAA-AA) Francoise Martinolle (-AAAAAAAAAA) Mehdi Mohtashemi (AAAAAAAAAAA) Neil Korpusik (AAAAAAAAAA-) Ray Ryan (AAAAAAAAAAA) Gordon Vreugdenhil (AAAAAA--AAA) Steven Sharp (--AAAA-A---) Phil Moorby (---AA-AAA-A) Doug Warmke (AAAAAAA---A) Stu Sutherland (-AAAA--AAAA) Heath Chambers (-AAAAAA-A--) Don Mills (--AA--A---A) Jonathan Bromley (--A--------) Logie Ramachandran (----AAAA---) Melvin Cardoza (-----A-AAAA) Mark Hartoog (-------A---) Satia (from Intel) (--------AAA) Rob Slater (Freescale) ^ |------- non-voting meeting ** Minutes taken by Neil Korpusik and Mehdi Mohtashemi ////////////////// January 8, 2007 ///////////////////////// Agenda: 1. IEEE patent policy ref: http://standards.ieee.org/board/pat/pat-slideset.ppt Neil: adopted new policy that will go into effect Move: Cliff - Assume that the patent policy was read Second: Heath Abstain: none Opposed: none passed 2. Review meeting minutes/Notes: The December 4th and December 18th minutes are not yet available on the web site. 3. Action items review ------------------------------------------------ AI on 890: (and related) [DONE] Francoise: contact svcc on pli regions Mentioned it to svcc, no concrete proposal yet, asked to forward. bring the new scheduling semantics proposal to the svcc when available. Doug: start with the changes in the 890 mantis (rev 5) [started] AI: Rob - send a summary of his use model to the alias. AI: Mehdi - contact svac, svcc about the proposed changes to section 9. AI: All - Cliff wants to know what issues are not backward compatible. AI: Steven - send examples of problems - so we can prepare. AI: Cliff - send out an example use of the program block (mostly for Rob) Cliff - has sent out a new scheduling semantics proposal. Action items: Previous meetings AI: follow-up to mantis 978 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. [DONE] AI: 553/1371: Dave Close 553 and place content of 553 in 1371. 4. P1800 meeting Jan 4th, update ----------------------------------- Patents: No impact on sv-ec for patents. The svac has new chairs John Havlicek (Freescale) as Chair Dmitry Korchemny (Intel) as Co-chair approximate time-line: Jan 15 --> Jan 31 LRM draft with current passed items available (editor's contract was delayed) Feb 20 P1800 F2F - review enhancements being reviewed Mar 15 Merged LRM available Oct 01 Intermediate draft -->Nov 15 Freeze on changes from committees (this is the new freeze date) The room at Mentor will be used by the P1800 from 10-1. The room will then be available for the SVEC to have a f2f (1-5) if it would like to have one. Proposals will need to be merged into the new merged doc. All changes that have been made since the last Champions meeting, assuming that we decide to move forward with the merged doc. Committees will do the merging (not the editor). All changes from Nov 9th onward. 5. Name Resolution sub-group update ------------------------------------ Gord: no update. 6. Continue review and discussion on Mantis 890 and related mantis items ------------------------------------------------------------------------- a) Rob's use model No input received. b) 890 08-31-06 clarifications in program and clocking blocks (Doug) Additional mantis items (there were no discussions on this set) 236 - should be resolved... ##0 239 - [CLOSED] 597 - [NOTE: look further down in the minutes-- CLOSED] 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 - [CLOSED] Program block exit semantics (Sharp) 551 - Program block interaction with queues (Sharp) 7. Additional mantis items ------------------------------------- 1623 - optional arg to timeunit declaration. - Steven - require parens if allow expressions in the future. Stu - bnf - 19.5 bnf change - looks like redundancies in the bnf. Steven - the bnf is spelling out the various possibilities. It isn't redundant. Doug - footnote 5 - for time_literal. Shall not be followed by a whitespace. What is this? Stu - no white-space between value and ps, fs, etc. Arturo - friendly amendment - get rid of extra carriage returns. Move: Heath - to approve proposal for mantis 1623, with friendly amendment. Second: Cliff Abstain: Dave - Would like SV-BC to review it. Opposed: none passed with one abstain Doug - #1step can be in procedural code Arturo - was meant for sampling but didn't feel a need to restrict it. 890 - event scheduling Cliff - new proposal for section 9 (890) - Diagram needs to be updated (re-inactive - capitals) - Request to editor to make global capitalization change is ok with Stu. (He was on the call) Jonathan - paragraph 5 on page 2, lexical spec no longer applies. Also see paragraph 4. Should be changed to "running in program context". Cliff - agrees Steven - need a name for the two inner loops AI/Cliff - update the proposal using new terms (active event regions and reactive event regions) Gord - this could be easy to misread Stu - don't capitalize the term "active event region set" Neil - Should reverse the direction of arrows on active region set. Will make it easy to visually see the symmetry between the two sets. AI/Cliff - update the figure to make it more clear there are two inner loops. Stu - do we need the sentence in last paragraph that refers to the IEEE 1364. Gord - likes the idea of keeping a reference to 1364. Neil - also likes the idea of keeping it in there Gord - wants it to be changed to 1364-2005. Stu - the IEEE might not allow us to refer to a specific version. Jonathan - para 4, page 2, - take out the word "conceptual" (twice) Stu - Last para, page 1, pre-re-nba - is this really part of 1364? Cliff - it should be pre-active AI/Cliff - change it to pre-active. Cliff - will have his proposal updated today. Stu - we should have 890 on the agenda for the P1800 meeting. - spend a few minutes on it in that meeting. Doug - will be at an svec f2f if we have it 597 - svac has closed a mantis item on this topic (1325). Move: Doug - close 597 as being covered by 1325 Second: Arturo Abstain: Opposed: passed Stu - 1325 isn't on list of changed to add to LRM. Neil - category is sv-lrm Stu - was able to find it when he sorted on sv-lrm AI/Stu - check with Karen on how to sort for the required LRM changes that he is currently working on. 608 - clocking drive resolution - this will be addressed by 890. 1707 - streaming - Dave dropped off the call when we reached this item. 1706 - virtual interfaces - Gord Gord - This mantis item spans both svbc and svec - always_comb for a virtual interface always_comb ignores other dynamic data types in sensitivity list - what about: continuous assignments procedural assignments How know if there is a drive conflict? mantis 1706 shows two possible solutions. Arturo - some procedural code is required to have virtual interfaces. Gord - was thinking you just ignore a virtual interface for always_comb Neil - what is the argument for ignoring it? Mark - classes are ignored today. Arturo - isn't it an error? Gord - for a dynamic reference - always ignore it... his suggestion. Mark - class function calls, can be virtual. - interfaces don't have virtual functions. Arturo - always_comb is meant to be combinational (for synthesis) Gord - 1. Participate in the sensitivity list? always_comb should have a static sensitivity list otherwise you could be sensitive to all possible static interfaces. Expressions use a separate set of calculus. 2. Error or not? Procedural continuous assignment - harder to agree on. Allow a continuous assignment through a virtual interface? Mark - a continuous assignment is not allowed in an interface itself. Gord - continuous assignment only allowed for a particular instance. Steven - what if virtual interface is null at beginning of simulation? Gord - could add a default instance to virtual interface. Mark - could use a hierarchical reference to get to it. Gord - prefers to not allow continuous assignments via a virtual interface Mark - procedural assignment to a null virtual interface? Gord - that is an error Gord - Would need to ensure virtual interface starts out non-null. But is it useful do allow it? Arturo - acts like a static interface in that case. Gord - anyone object to this? (not allowing it) [no one disagreed] Mark - can still do continuous assign via a hierarchical reference (half of the problem would still remain) Steven - One shouldn't be using procedural assignments to anything that is part of a continuous assign. - dynamic objects - statement in LRM about restrictions Gord - a virtual interface is a virtual reference to a static interface. AI/Gord - will put something together for review. 8. Next meetings -------------------------------------- January 22, 2007 Monday, 11:00-1:00pm Feb 5th, Feb 19th is a holiday -- No meeting Feb 20 is possible Face-to-face meeting, there is a p1800 meeting from 11-1:00 sv-ec can have 1:00 to 3:00pm. DVCon07 is during that week March 5 Who won't be in town for DVCON? Gord - can attend a F2F on 2/20 FM - a good chance she will be in town Steven - will not be in town, could dial in ========== ADDITION TO the minutes, not part of regular ========= ========== meeting discussions, informational purposes ========= ========== Action Items updated based on January 8 2007 ==== Action items: January 8 2007 ------------------------- AI: 890 and related items: Cliff - update the proposal using new terms (active event regions and reactive event regions) Cliff - update the figure to make it more clear there are two inner loops. Cliff - Last paragraph page 1 -- change it to pre-active. AI: 1325 Stu: check with Karen on how to sort for the required LRM changes that he is currently working on. AI: 1706 Gord: will put something together for review.