Subject: The SV Chairs Process for SV 3.1 LRM standardization
From: Vassilios.Gerousis@Infineon.Com
Date: Fri Sep 13 2002 - 00:26:05 PDT
Hello SV members,
As promised, the SV chairs have put together the process for the
development of 3.1 LRM and the standardization completion by DAC 2003.
We solicit your feedback.
We have taken several inputs from the members of this committee. The SV
Chairs primary objective is to be efficient to operate as an organization,
and also follow a formal process to get the job done. Everyone (chairs and
members) is now committed to execute and get the job done that we outlined.
We have assembled an impressive talents and dedicated members to help to
make this a success. Let us roll.
in terms of the LRM, we have the following:
1- We will have one LRM for SV 3.1.
2- The primary SV 3.1 editor is Stuart Sutherland. Yatin will help Stuart to
edit C/API portion. This way Stuart can focus on immediate job for the basic
committee and provide assistance to other SV committees.
3- Stuart will work directly with the SV chairs to get each portion of the
LRM planned and organized.
SV 3.1 LRM and Standardization PROCESS
----------------------------------------
1- Established 4 committees, Each is responsible for:
a- Technical content within their committee.
b- Implement interfaces or enhancement requested by the other
committees.
2- A joint committee is assembled (SV)
a- Review Progress.
b- Synchronize.
c- Review the assembled LRM. Partial assembly will be done.
3- LRM Development:
a- Each committee will address the current available donated
materials.
b- Each committee will vote to accept/reject donations. If portions
are accepted. the donation is accepted.
c- Each committee will develop an LRM portion of the donated
material.
d- Each committee will make available to the other committee any
request to enhance certain capability for the committee required. (e.g. SV
language for using C model or task should be ??)
e- Other committee must address the request with action.
f- Joint meeting if necessary should be done to address common
things.
4- Review and Voting:
a- Each committee develop and build an LRM portion.
c- Each committee allocate time to review and vote on final draft.
d- A full LRM should be assembled as soon as all materials are
ready.
e- Each committee review their content "in context of the LRM" also.
f- The full committee review the final draft of the LRM. Any
changes, is sent back to the appropriate committee for modification.
g- When all issues are resolved by each of the committees the
full committee then votes on sending the final draft of the LRM to the
Accellera board.
5- SV 3.0 Issues And Enhancement List: We have assembled an impressive list
of enhancement and issues based on SystemVerilog 3.0 standard.
a- A deadline is set for end September to provide owners a final
chance to submit a proposal. No proposal, by that date, will automatically
remove that item from SystemVerilog 3.1 release.
b- Feedback on SV 3.0 implementation will be added to the list
automatically and given the highest priority for resolution.
c- SV 3.0 issues list and enhancement will be closed at the end of
December.
d- Feedback on SV 3.0 implementation will continue until the final
draft is completed and voted on.
Best Regards
Vassilios
This archive was generated by hypermail 2b28 : Fri Sep 13 2002 - 00:30:18 PDT