Minutes of ISAC meeting held via telecom on 06 October 2005 Present: Peter Ashenden, Jim Lewis, Chuck Swart, Ajay Verikat Absent: Deepak Pant, Larry Soule Next Meeting: Thursday November 10, 2005, 6 pm Pacific Standard Time (Friday November 11, 2005, 2 am GMT) TOPIC: Revisions of approved IRs There are some IR which were approved by the VASG but, in response to comments, were revised. We did not resubmit them to the VASG for re-ballot because of VHDL200X activities. Since the Fast Track activities have been taken over by Accellera, it is appropriate to move forward with these ISAC issues. ACTION: Chuck to prepare list. Peter to submit to VASG. TOPIC: Status of Web Based IR System Little work has been done on this since the last meeting. The system is available at: https://bugzilla.mentor.com ACTION: Jim and Deepak need to login and get user accounts. TOPIC: IR 2074 Problem with direct/select visibility in formal part There was general agreement that there should be a clear rule regarding visibility when one declaration is visible directly and another declaration with the same name is visible by selection. There was no compelling rational for selecting one form over the over, but it seems (slightly) preferable that visibility by selection hides direct visibility. ACTION: Chuck and Ajay to analyze. TOPIC: IR 2070 Support for floating point denormal numbers Peter has asked to give up his IRs because of other commitments. ACTION: Chuck will analyze and submit for vote. TOPIC: IR 2038 Minor semantic errors Peter has asked to give up his IRs because of other commitments. ACTION: Someone needs to take this up. TOPIC: IR 2054 Individual assoc. rules for array formal are not valid No activity. ACTION: Chuck to check with Larry on the status of this IR. TOPIC: IR 2071 Indexed name in case expression This IR has been superseded by FT 25: Remove restrictions on static subtype for case expression. Note that if FT 25 is not adopted then we will need to revisit this issue. ACTION: Chuck to forward to VASG. TOPIC: IR 2072 Allow static operations on "ranges" It was observed that a range could be thought of as a record with Left, Right and Direction fields. Much of what the submitter wants could be implemented today using aliases. A more complete use case would be helpful. ACTION: Chuck to contact submitter to ask for a more complete use case. TOPIC: IR 2073 Index constraints and discrete range conversions from universal_integer No problems have been uncovered in relaxing this constraint. ACTION: Chuck to complete analysis. TOPIC: Categorization of Old IRs No activity. ACTION: All to review their assigned IRs.Received on Mon Oct 17 13:19:12 2005
This archive was generated by hypermail 2.1.8 : Mon Oct 17 2005 - 13:19:24 PDT