SV-EC Committee Meeting Monday May 8 2006 11:00am - 1:00pm PST [Minutes distributed for approval at next (sv-ec) committee meeting] (10211210 ) Day (99333708 ) (10000000 ) Month (21123345 ) (00000000 ) Year (56666666 ) --------- Attendees ---------- (AAAAAAAA ) Arturo Salz (-AAA-A-A ) Cliff Cummings (A-AAAAAA ) Dave Rich (AAAAAAAA ) Francoise Martinolle (AAAAAAAA ) Mehdi Mohtashemi (AAAAAAAA ) Neil Korpusik (AAAAAAaA ) Ray Ryan (--AAAaaA ) Surrendra Dudani (-AAAAA-A ) Gordon Vreugdenhil (----AAAA ) Steven Sharp (-A--AA-- ) Phil Moorby (AA------ ) Doug Warmke (---AAA-- ) Stu Sutherland (-----a-- ) Don Mills (Aa------ ) Chris Spear (-------- ) Brad Pierce (-------- ) Karen Pieper ^^------------ Considered ONE MEETING. ** Minutes taken by Neil Korpusik and Mehdi Mohtashemi ////////////////// May 08, 2006 ///////////////////////// Agenda: 1. IEEE patent policy ref: http://standards.ieee.org/board/pat/pat-slideset.ppt Move: Gord - Assume that the patent policy was read Second: Arturo Abstain: none Opposed: none passed 2) Review Meeting minutes, of March 27th, 2006 meeting Motion: Dave - approve meeting minutes of March 27, 2006 Second: Ray Oppose: none Abstain: none Passed Unanimously The minutes for April 10th is left for next time. 3. Review Action item list: Action items: April 10, 2006 ----------------------------- AI: 1330 Dave: add an example (not done yet) AI: 1279 Ray: discuss over email for next meeting. Create list of questions that need to be resolved (was sent out last Thursday - May/4th) AI: 1279 Mehdi: check with Brad on syntax boxes that don't appear in the appendix. What does it mean to have a syntax diagram which isn't in the appendix? : syntax box in 18.6 not in Annex A (no feedback from Brad. Mehdi will check with Karen) AI: 261/262 Steven: put together some examples of overflow (not done yet) AI: 261/262 Arturo: unsigned/signed examples. (not done yet) AI: 261/262 Neil: try to find some randcase examples with expressions being used. (done - most use constants) AI: wait_fork & disable_fork. Dave: create mantis item for sub-clauses (in 11.8.1, 11.8.2) (mantis 1451 was created) AI: 'this' question from M. Burns, Dave: review and discuss with Gord and create a mantis item. Using this as the default value of an argument. (no mantis item yet) AI: Mehdi: will move closed (approved but placed in closed state) mantis items to the acknowledged state. (done) Action items: March 27 2006 ---------------------------- AI: 1306: Steven: create a new mantis item for the case foreach where no variable has been specified. (1415 was created) AI: 1306 Ray: Add a bug note to this mantis item. (not done) (can probably get rid of this) AI: 261/262 combined - Steven, put the proposals together, should address both 261 and 262. and vote on it next time. (so far Steven and Arturo are the only two offering opinions and they disagree) AI: 247 Ray - close 247, create a new mantis item for static randc issue (1416 was created and resolved) Action items: March 13, 2006 ---------------------------- AI: new item - Gordon to create a new mantis item for randomize() method call item (Ray and Gordon have discussed - still working on it internally) Action items: February 13, 2006 ------------------------------- AI: Ray - add a new Mantis item for the visibility issue. (1279 - ???) 4. Continue with Mantis items: 1279, clarify covergroup/point/cross Ray: sent out email on this 1279. Arturo: some items not clear, key question, lexical regions create scope where do you search. Ray: coverpoint create name, do they create name space. Gord: relationship between covergroup (new argument) and implicitly named covergroup. Arturo: reference x, conflicts with label x. Gord: x: coverpoint x; // should be ok Possible issues 1)implicitly named coverpoints 2) arguments region 4 of example in item 3) x.option.weight // which x? Neil: if it is not labled, defaults. Arturo: that refers to something that lies outside of covergroup or one of the arguemnts. Gord: any case within a coverpoint, legally referenc a property of a covergroup. Arturo: I think we should exclude that, make it an error. Gord: an example, Is the following legal? a : coverpoint a { a.option.auto_bin_max = 128; } perhaps indicate within a covergroup we are not allowed to specify a covergroup name Ray: a.option.auto_bin_max outside of coverpoint would refer to coverpoint a. Arturo: Never search the coverpoint names except within a cross. when a global instance of a covergroup (foo) exists foo.x.option.weight can be used as part of a coverpoint expression. Gord: can refer to coverpoints from outside the covergroup arguments are like properties of the covergroup constructor example at top of page 323 gc::a::type_option.weight = 3; type_option is a static member, so :: is valid a covergroup is a unique beast since the rules are different from refering to them internally versus externally (internally don't look at coverpoint names). Ray: gc:: can only be used outside of the covergroup? Arturo: there doesn't seem to be a need to be able to access coverpoints internally except for crosses. Doing so would add a lot of complexity. a coverpoint creates a scope Gord: the novel look-up rules seem to be easy to describe (e.g. can only internally refer to a coverpoint label in a cross). Ray: if a coverpoint creates an anonymous type, would disallow :: syntax. Gord:just say coverpoints allow :: syntax (without saying why to avoid confusion) agrees with the proposal at the conceptual level. AI: Ray and Gord, to put the proposal together for 1279. Possibly get rid of some of the syntax boxes (those not in Annex A). Randomization/Constraint related -------------------------------- 884 incorrect interpretation of expression in constraint example Motion: Francoise - approve the proposal for mantis 884 Second: Cliff Oppose: none Abstain: none Passed Unanimously 270 need more information when randomize method fails This is an enhancement request. We don't have a PAR yet and so we are not allowed to work on enhancement requests as a committee. The intent would be to only work on enhancements that don't have widespread effects. 262 randcase unclear (assigned) 261 randcase width rules (assigned) Neil: found examples with constants, most of the time value 1, few places variables used. value would be done prior to the randcase. no complicated expression Waiting on input from Arturo and Steven. ( AI:Steven - put together some examples of overflow ( AI:Arturo - unsigned/signed examples. 211 built-in scope randomize (assigned) Gord: randomize() issues. Deals with same stuff as the AI for Ray and Gord. Ray: the document for 211 is out of date. Gord: will still open a new mantis (can refer to 211) Miscellaneous: -------------- 1270 xor, maybe covered by 978 Motion: Dave - Close as a duplicate of 978. Second: Steven Oppose: none Abstain: none Passed Unanimously 1256 description of linked list (annex D) Gord: description in annex D conflicts with parametrized class type `include conflicts with classes it should be in package. Arturo: standard include directory area, `include Gord: useful way to provide vendors to provide things, move it to standard package. before packages before parametrized classes, Steven: functionality is like queue. Arturo: there is a lot of overlap, Gord: there is one method purge(), like to remove from list, can not be written in SV, side effects on prefex of the call to purge D.6.18, it is not clear list1.purge, you actually modify the object reference. like passing this by reference it should be struck. Arturo: that would be the intent. mixes automatic and explicit memory management. Gord: number of reasons, re-written as regular SV, the whole thing as SV. semantics not describalbe in SV. Arturo: you could describe it if this is passed as an arguement. Steven: that would not work, this would not be, this is itself a copy of the handle, so it would not work. Arturo: linked lists came about before packages were defined lists can have handles to the elements. Steven: is it related to garbage collection. Gord: implied memory management is mis leading, implied behaviour leave it open, if there is nothing special about list, why define it as in LRM. then strike it if part of pacakge standard, then it is ok. STL-like library - would rather have a more complete set. Steven: if we got rid of purge, then users can use it as source. Gord: I would be prepared to strike it out completely. until the PAR comes up. Neil: as part of NTB and Vera use it, alot of people would use it if it were there. Steven: an STL-like library could be a separate standard (or dot-standard) Gord: willing to delete all of annex D. Arturo: `include <> could just import the package General agreement on purge() and `include issues. AI/Gord - will add some comments (bug notes) to mantis 1256. 1168 missing colors in A.2.10, A.6.11, A.6.12 Motion: Cliff - approve proposal for 1168 Second: Gord Oppose: none Abstain: none Passed Unanimously 1038 array ordering methods No proposal. 978 5.15 array methods, AI: Neil - redo the proposal - not a real proposal yet. 976 5.9-5.10 clarifications AI: Dave - put a proper proposal in place. 975 related to 5.9, illegal for index_type Wait for 976 to be done first. 974 dynamic arrays/queues comparison 968 list package - will be covered by 1256 960 one dimension (assigned) - Doug Warmke is working on something related to this with Ralph Duncan. mantis 1447 AI: Mehdi - discuss this with Matt to resolve the overlap. AI:Mehdi - sort the lists by those that have proposals (immediate items). 5. next meeting: May 22nd 2006 Also discuss the following meeting time frame, as we enter June-July (pre DAC activities). ======================================================================= ================= Action Items =========================== Action items: May 8, 2006 ------------------------- AI: 1256 Gord - will add some comments (bug notes) to mantis 1256. AI: 978 Neil - redo the proposal, not a real proposal yet. AI: 976 Dave - put a proper proposal in place AI: 960 Mehdi - discuss this with Matt to resolve the overlap. AI: general: sort list by items with proper proposal. (some are marked immediate Action items: April 10, 2006 ----------------------------- AI: 1330 Dave, add the example list to do. AI: 1279 Ray: discuss over email for next time create list of questions that need to be resolved Mehdi: check with Brad on syntax boxes that don't appear in the appendix. What does it mean to have a syntax diagram which isn't in the appendix? : synatx box in 18.6 not in Annex A No input Brad, I will check with Karen. AI: 261/262 combined Steven put together some examples of overflow -- Arturo unsigned/signed examples. AI: 'this' question from M. Burns, Dave: review and discuss with Gord and create a mantis item. (this as a default argument ) Action items: March 27 2006 ---------------------------- AI: 1306 Ray a bug note to this mantis item. may want to drop. =================== Resolved Mantis items ============================= Resolved Mantis items (by dates) --------------------------------------------------------------- May 8, 2006 (state) --------------------------------------------------------------- 884 approved Unanimously 1270 CLOSED covered by 978 1168 approved unanimously -------------------------------------------------------------------- April 10, 2006 (state) -------------------------------------------------------------------- 1308 approved with one abstain (Steven) 1416 approved with one abstain (Steven) Resolved Mantis items (by dates) -------------------------------------------------------------------- March 27, 2006 (state) -------------------------------------------------------------------- 1306 approved acknowledged 1315 approved acknowledged 1393 approved acknowledged 1357 approved acknowledged 247 Closed --> closed 270 remains as enhancement 134 reamins as enhancement -------------------------------------------------------------------- March 13, 2006 (state) -------------------------------------------------------------------- 714 approved assigned 892 approved assinged 1242 approved assigned [ one abstain] 1243 approved assigned 1244 approved assigned 1263 approved assinged Reviewed items from other committees 1325 SV-AC February 13, 2006 -------------------------------------------------------------------- 138 approved assigned enhancement 251 - no action - assigned enhancement 253 approved closed 1178 approved closed 1237 approved assigned 1239 approved assigned 1240 approved assigned January 9, 23 2006 items -------------------------------------------------------------------- 344 closed 644 closed 683 approved closed 712 approved closed 722 approved acknowledged 725 approved closed 1236 approved assinged 1238 merged with 1237 closed =======================================================================