Minutes Taken by Stefen for 1/13/03 meeting: Attendees: 0111110000 \ 1221109998 / Month 1101022002 \ 3628413996 / Day aaaaaaa*aa Steven Sharp aaaaa-a*aa Karen Pieper -aa--a-$aa Cliff Cummings aaaaaaa=-a Shalom Bresticker aaaaaaa*aa Stefen Boyd aaaaaaa*aa Dennis Marsa aaa-aaa$aa James Markevitch aaaaaa-=-a Gordon Vreugdenhil a-aaaaa$aa Anders Nordstrom ---aaa-$a- Ted Elkind aaaaa-a*a- Brad Pierce -aaaaaa*a- Charles Dawson -a-aa-$a- Mike McNamara aaaa---*aa Stu Sutherland -------*a- Tom Fitzpatrick -------*aa Elliot Mednick Steven Sharp Karen proposed email voting on simple issues - 10 to 15 each week Anders - Shouldn't this be at a meeting. What's the difference? Karen - It avoids problem of reviewing items at the meeting. Anders - Since it's still able to be reviewed one more time in the VSG, that should be ok. Stefen proposes accepting minutes with only change being that next meeting was 1/13 not 12/16.. Karen second passes (Pre 11/4/02) Cliff still to analyze issue 9 and 13. 9 is not done. Truncation rules not defined. Experiments in progress. Padding rules not clearly defined. Issue with signed unsigned in context of x and z. Rhs size calculations are made in the calculation of the right hand side. Assignment is to same width objects. 13. Proposal sent out. Cliff will update the database page with the proposal. (Pre 11/4/02) Issue 28, new proposal from Cliff pending. Done (11/4/02) Steven will proposing a wording to fix 172. Testing done. Proposal not made. Steven - Still working on wording having to do with bit and part selects. Problem is that VCS might allow bit or part select of scalar Gordon - Does the standard allow it? Steven - If we don't deal with handling of bit or part select, it has impact on implicit nets Shalom - Who says it creates a scalar? Steven - That's what we already passed and was discussed Shalom - Never discussed bit or part select. Steven - Did agree that it should work the same way as if on port expression. Will make wording clear about error. Also fixing bit and part select on port since it's not clear about port errors. (11/18/02) Gord and committee to return with a generate proposal for 113, 17. Waiting for feedback on the original writeup. No feedback made. Gordon - Much discussion on this over last couple weeks. Need more concise wording. Making progress. Karen - "A lot of impact" - does that mean a lot of changes to the manual Shalom - We need to change things like hierarchical name references to make it work Gordon - Lot's of work to do, but getting closer to LRM wording. Subgroup making progress. Karen - Are we going to be able to make this work while maintaining backwards compatibility? Gordon - Also affect arrays of instances. Steven - Some issues with inconsistent wording. Gordon noticed at least one issue with hierarchical names. Gordon - Do we want to specify pseudo code or just describe working of final state without the algorithm. Worried about over-constraining or leaving big holes. Stefen - Timeline for proposal? Steven - After power operator worked out. Gordon - We are actually releasing a version with initial version of generate. Will want it finalized by mid February. Steven - Mostly settled, just corner cases is what will cause most pain. Gordon - Name clashes or defparams are corner cases. (11/18/02) Dennis and committee to return with a power operator proposal for 140 Lots of discussion. One proposal made and under consideration. Stefen - So this is on schedule for wrap by end of month? Dennis - Had good discussion that died out over hollidays Shalom - Have draft of rewording of proposal. Can send draft out. Steven - Has proposal that changes the technical content Gordon - Should have possibly competing proposals by next meeting. (11/18/02) Steven and committee to return with an @* proposal for issues 22, 82, 84 To be resolved after power and generate. Steven - Holding off on that. We've already released our @*. Once generate is wrapped up we'll work on this. Gordon - Won't be done with generate until beginning of March (11/18/02) Evaluating TBD Errata. The tasks are: Steven 96 Errata ambiguity in 4.1.12 on the >>> operator 117 19.1,19.6,19.9: `unconnected_drive and `celldefine Lots of hard ones. Karen 123 Fwd: identifier and indexing syntax Gord 165 13.11.1, A.2.1.1 -- reuse task_port_type 170 formatting of bnf non-terminals 172 3.5 Implicit Declarations - moved from #125B Anders 175 13.2: file_path_spec syntax and related issues Brad 189 12.1, macromodule needs clarification Charles 197 198 No one has made further progress. (12/2/02) Shalom to propose new wording for 174. Shalom - Low priority, but will let it go as is. Karen - Do you want to pull it off to reword? Shalom - No, just submit new proposal. AI - Shalom to submit new issue for rewording of 174 (12/16/02) Steven to file an issue on 64-bit chi-square. Steven - Looked at it as not entirely necessary. Shalom - Category is enhancement, class is errata. Gordon - Not worried about porting issues. Wouldn't even address. Shalom - I'll change the class to be consistent with category... done. SV-BC Issues requiring resolution: (ETF issue number: SV-BC issue number) 85: 19-35 200: 19-21, 19-24, 19-26 133: 19-1 136: 19-3, 19-5 181: 19-49, 19-52, 19-55 182: 19-31 193: 19-16, 19-17 202: 19-23 -232: 19-37 -237: 19-41, 19-42 -238: 19-45, 19-47 (* have proposals) Issues to discuss: 20 -- Shalom has updated the entry with his proposal Shalom - already discussed and had competing proposals. I compressed it by removing an extra level of definitions. One technical change was that semicolons were not added to parameter definitions (Issue 114). Brad - Did 114 cover all that was left out of #20? Shalom - Do not deal with same lines of bnf Propose 20 - Shalom, Brad second, passes 89 -- Shalom has updated the entry with his proposal Shalom - They are allowed, but added examples. 218 is separate issue for nested. Propose 89 - Shalom proposing, James second, passes Propose 218 - Gordon proposed, Shalom second, passes Anders - but don't we have to fix bnf? Gordon - too much work , semantic check is better Meeting adjourned for start of VSG meeting Next Meeting is 1/27/03 at 8:30am Pacific.