SV-EC Ballot resolution committee meeting. Monday May 11 2009 11:00am - 1:00pm PDT [ http://www.eda.org/sv-ec/Minutes/SV-EC_Meeting_May_11_2009_Minutes.txt ] Meeting number: ------------------------------------------------------------------------- 00000 00000 11234 Meeting Days: ------------------------------------------------------------------------ (12201 ) Day (30741 ) (00000 ) Month (44455 ) (00000 ) Year (99999 ) ------ Attendees -------------------------------------------------------- (A-AAA) Arturo Salz 4 (A-AAA) Cliff Cummings 4 (AAAAA) Dave Rich 4 (AAAAA) Francoise Martinolle 4 (AAAAA) Mehdi Mohtashemi 4 (AAAAA) Neil Korpusik 4 (AAAAA) Ray Ryan 4 (-AAAA) Gordon Vreugdenhil 4 (AAAAA) Steven Sharp 4 (A-AAA) Stu Sutherland 4 (AAAAA) Heath Chambers 4 (AAAAA) Don Mills 4 (AAAAA) Jonathan Bromley 4 (AAAAA) Mark Hartoog 4 (AAAAA) Tom Alsop 4 (A-A-A) Mike Mintz 3 (AAAAA) David Scott 4 17 members have joined the call; 3 of the 4 meetings had 17 people on-line. ** Minutes taken by Neil Korpusik and Mehdi Mohtashemi ////////////////// May 11 2009 ///////////////////////// Agenda: 1. Review IEEE patent policy ref: http://standards.ieee.org/board/pat/pat-slideset.ppt Move: Heath - assume patent policy was read Second: Mark Abstain: None Opposed: None Approved 2. Approving previous meeting minutes. --------------------------------------- May 4 2009 [not yet available on the sv-ec site] 3. Updates from p1800WG / ------------------------------------------------------ The P1800 meeting was last Thursday May 7th. Neil: still working towards the May 14th deadline. sv-ec said we will not complete. 4. Ballot Comments reviews --------------------------------------------------------- 4.1 request from BC to review 2692, 2380 (Cliff) The BC unanimously voted this issue to be better suited for SV-EC: http://www.eda-stds.org/svdb/view.php?id=2692 By cancelling the email vote, we will be able to address those issues today. move: Neil - cancel the email vote that is ending on May 13th. second: Cliff abstain: none opposed: none Passed unanimously Mantis 2700 id 37, 38 move: Jonathan - approve the proposal for mantis 2700 (-2 version) second: Gord abstain: none opposed: none Passed unanimously Stu - first para, string literal and string type, need keyword font. - Stu will take care of it during the editing process. He looks correct about his concern. Mantis 2514 id 182 move: Jonathan - approve the latest proposal for Mantis 2514 (version 2514-2.clean) second: Cliff abstain: none opposed: none Passed unanimously Gord - delete the earlier proposals after this is approved. Mantis 2510 id 183 Neil - doesn't understand it Arturo - see 6.21 last sentence of last paragraph for the relevant text move: Dave - approve the proposal for mantis 2510 second: Cliff abstain: none opposed: none Passed unanimously Mantis 2342 id 185, move: Steven - approve the proposal for mantis 2342 second: Cliff abstain: none opposed: none Passed unanimously Mantis 2288 id 186, 2288_next_prev.pdf move: Dave - approve the proposal for mantis 2288 second: Cliff abstain: none opposed: none Passed unanimously Mantis 2575 David - had an issue with mentioning covergroups Arturo - if use handle.parameter what is the result? Gord - it would be a value Arturo - that is odd Gord - it is a dynamic reference Arturo - they are local params and can't be overridden - it would open a whole can of worms - it is a constant expression Steven - constant expression has a definition in the LRM. Arturo - there is a mechanism to get to them (class resolution operator) Mark - handle reference, is it only to the parameter in that instance? Dave - param in a module, it is legal, if use hierarchical reference it is illegal. - a dotted reference is a simple rule, doesn't think there is any confusion . Gord - only need details of the parameter not the handle. - they are constant expressions (see proposal) - doesn't see that we are taking away any existing functionality. Arturo - 8.17 "accessto" (missing space) - in the syntax - there should be some superscripts (for footnotes) Stu - the superscripts are not a problem for the Editor Neil - 2575 is currently assigned to the sv-bc (id 50, 52, 55, 59, 64) No changes to 8.24.1 in this proposal. Took out changes for 64 Move: Arturo - approve the proposal for 2575 - approve the proposal for 2598 - close 2608 as being addressed by 2575 Second: Gord Abstain: none Opposed: none Passed unanimously Arturo, Gord 2598 is in sv-ec (id 52, 64) consistent with 2575. Arturo wants to keep this one open. 8.24.1 is modified in this proposal 2608 will also be resolved if 2575 is resolved. Mantis 2597, id 49 Gord - v3 proposal, class property initialization and construction - "The value of a property prior to its initialization shall be undefined." Arturo - it is a bit contrived... (agreed) - there could possibly be some friendly amendments? "the new method of a derived class" (2nd sentence) Gord - this will most likely cause some changes to various implementations move: Gord - approve the proposal for mantis 2597 (version v4) 2597_class_initialization_v4.pdf second: steven abstain: none opposed: none Passed unanimously Mantis 2738, id 115 AI: Tom - mantis 2738 id 115 reload as a pdf (Neil can't see it). Mantis 2729, id 30, 31 move: Arturo - approve the proposal for mantis 2729 second: Jonathan abstain: none opposed: none Passed unanimously Mantis 2730, id 114 move: Arturo - approve the proposal for mantis 2730 second: David abstain: none opposed: none Passed Unanimously Mantis 2712, id 116 Steven - had a question about a wildcard in the situation where there is a range. - there is no operator to handle < or > for a wildcard item David - 19.5.3 covers wildcards Steven - this text now says it is allowed (in addition to a wildcard) David - removed the 3rd piece of blue text. If an element of a bins open_range_list is a range [b1 : b2] and either b1 or b2 contains any x or z bits or every value in the range would generate a warning, then the element shall not participate in the bins values. ---> This rule cannot apply to wildcard bins because x and z shall be treated as 0 and 1 as described above. <--- move: David - approve the proposal for mantis 2712 (version -2.pdf) second: Jonathan abstain: none opposed: none Passed unanimously "this rule cannot apply" ==> stu will work with Shalom Mantis 2693, id 138 Neil - was discussed in the April 27th meeting Arturo - strike the 2nd sentence - it is confusing what is being said Stu - notes are not binding text in the LRM Steven - the last para in the proposal (drop the first two words "Note that") Now it would say "In addition to... 5. The remaining ids -------------------------------- 21 51 2724 Gord, Arturo - approve the proposal for mantis 2724 passed unanimously 53 55 59 2608 -- 62 2606 -- the current LRM is sufficient (Gord) -- no proposal 63 2607 -- 81 -- svac - no change required 101 2562 -- was resolved by the svac 109 110 111 113 121 134 135 138 2693 -- 140 2694 -- no proposal 184 188 189 190 192 79 2692 --- from svbc -- we really don't have time to do anything now... xx 2380 --- from svbc AI: All - last chance to point out anything that people want to work on. Note: next WG meeting will be on May 28th. 6. Next meetings --------------------------------- None currently scheduled. === action items list below is provided for members reference === not part of official meeting minutes ================= Action item list provided for sv-ec =================== ============ from May 11 2009 meeting =================== AI: Tom - mantis 2738 id 115 reload as a pdf (Neil can't see it). AI: All - last chance to point out anything that people want to work on. ============ from May 4 2009 meeting =================== AI: Francoise - put a proposal for id 19. AI: Mehdi - put mantis 2700 up for an email vote. AI: Steven - mantis 2713 update with a reference to "text above" AI: Mehdi - update 2719: friendly amendment for id 60 and remove id 122 AI: Mehdi - for 2711, check the rules for voting, yes/no/abstain items. AI: Tom - write a proposal for id 115 AI: Mehdi - for id 182 mantis 2514 put the proposal into an email vote AI: Dave - id 183 mantis 2510 will update the proposal to have a xref to 6.21. AI: Mehdi - id 183 mantis 2510 put up for an email vote AI: Arturo - send email on mantis 2597, id 49. AI: All - send email for any that remain open that should be done for this PAR. ============ from April 27 2009 meeting =================== AI: Stu - id 42; write a proposal (the third 'is'). Dave mentioned a second spot also. AI: Jonathan - id 138 put together a proposal (in the coverage section) AI: Mehdi - id 140 put into email vote - consider for next PAR. AI: Gord - id 52 and 64 create a proposal for an update to 8.22. Won't have time to review the whole LRM for other places to change. AI: Francoise - id 52 and 64 will make a more complete proposal. AI: Gord - id 51 will put together a proposal. AI: All - ids 67,53,55,109,111,49 send email on it. AI: Steven - id 21, will gather some input on this. mantis 2715 AI: Steven, Arturo, Gord - review the set of points in mantis 2715 (id 21) AI: Dave - send email to Mehdi on the mantis items that address his AI/s ============ from April 20 2009 continuation meeting =================== AI: Steven - row 146 id 47 create a proposal for updating the table. AI: Mehdi - row 148 id 48 add to an email vote, one of the canned responses should work. AI: Francoise - row 149 id 49 will add and email link to the mantis item. AI: Steven - row 150 id 50 will track down what text he thinks needs to be changed so that we can think of these as class members. AI: Francoise - will have a proposal by next meeting. AI: Arturo - row 151 id 51: take a look at this one (and line 152 id 52) AI: Francoise - add to mantis 2575 (line 150, id 50) AI: Mark - row 153 id 67write up a proposal AI: Francoise - row 154 id 53 write a proposal to move that one sentence earlier in this section. AI: Jonathan - row 158 id 182 will take a look at it. AI: Mehdi - row 167 id 183 add to the email vote. ================= Action item list provided for sv-ec =================== ============ from April 13 2009 meeting =================== AI: Mehdi - conduct an email vote on the trivial items.[requires proposals] AI: Steven - row 128, id 20; put together a proposal, mantis 2634 AI: Steven - row 130, id 21, will gather some input on this. AI: Dave - row 131, id 184; put together a proposal. AI: Arturo - row 132, 133, id 30 & 31; write it up, both 132 and 133 AI: Stu - row 134, id 35; writeup a proposal AI: Jonathan - combine rows 135-139 [ids: 36-40] into one mantis item. AI: Dave - row 140, id 186; put together a proposal. AI: Dave - row 141, id 43; put together a proposal for this AI: Jonathan - row 142, id 44; will put together a proposal. AI: Dave - row 143, id 188; will look into 141, 144 AI: Dave - row 144, id 45; combine this with row 141, id 43 AI: Stu - row 145, id 46; will write a proposal AI: Dave - row 147, id 181; follow-up on thisfor now AI: Gord - row 149, id 49 [not here, but on his list to discuss/review] AI: Francoise - row 150, id 50; will follow-up for now AI: Francoise & Gord - row 151, id 51; will follow-up for now AI: Francoise - row 152, id 52; will follow-up AI: Francoise - row 153, id 67; will look at it. AI: Francoise - row 154, id 53; will follow-up. AI: Francoise - row 156, id 55; will follow-up, non-trvial AI: Cliff - row 157, id 57; put together a proposal AI: Dave - row 158, id 182; follow-up, proposal, maybe trivial. AI: Mehdi - row 159, id 58; editoral, assign to editor. AI: Gord - row 160, id 59; related to id 50. AI: Mehdi - row 160, id 60; editoral, assign to editor AI: Mehdi - row 162, id 61; editoral, assign to editor AI: Gord, & Francoise - rows 163-166, id [59-62]; to follow-up. AI: Dave - row 167, id 183; follow-up, non-trivial AI: Mehdi - row 168, id 80; proposal exists, add to email vote AI: Mehdi - row 169, id 81; send to sv-ac; sv-ec has no change to recommend. AI: Mehdi - row 170, id 101; send to sv-ac AI: Ray - row 171, id 102; put together a proposal AI: Dave - row 172, id 102; follow-up, nontrivial AI: Dave - row 173, id 190; follow-up, nontrivial AI: Mehdi - row 174, id 104; assign to editor. AI: David Scott - row 175, id 105, follow-up, non-trivial AI: David Scott - row 176, id 106, follow-up, maybe trivial AI: David Scott - row 177, id 107, follow-up, non-trivial AI: Mehdi - row 178, id 108; assign to editor. AI: Francoise - row 179, id 109; try to get more information AI: David Scott - row 180, id 110; make sure it is a duplicate AI: Francoise - row 181, id 111; get more clarification. AI: Mehdi - row 182, id 112, assign to editor AI: David Scott - row 183, id 113, follow-up, trivial. AI: Arturo - row 184, id 114, put a proposal together; non-trivial AI: Mehdi - row 185, id 115; no change needed AI: David Scott , Gord - row 186, id 116; follow-up. non-trivial AI: Mehdi - row 187, id 117; assign to editor AI: Mehdi - ro2 188, id 118; assign to editor AI: Mehdi - ro2 189, id 119; assign to editor AI: David Scott- row 190, id 121; follow-up, non-trivial. AI: Mehdi - row 191, id 122; assign to editor AI: Arturo - row 192, id 120, follow-up, non-trivial. AI: Mehdi - row 193, id 134; send it to the sv-bc AI: Mehdi - row 194, id 135; send it to the sv-bc (duplicate of id 134) AI: Mehdi - row 195, id 137; assign to editor AI: Dave - row 196, id 185; follow-up, trivial. AI: Dave - row 197, id 192; follow-up, non-trivial.