RE: [sv-cc] Change "P1800-2005" in Annex F and G?

We may want to provide a uniform mechanism for this versioning
together with a way of versioning the VPI implementation.
The SV-CC is aware that successive versions of the 1364
standard specify VPI models that are not strictly compatible
with each other.  In addition, they are not always compatible
with the VPI model specified by 1800-2005, and we may
expect further incompatibilities in 1800-2008.

So perhaps we should look for a uniform way to determine
version of the standard that the implementation is currently
supporting.

(1) Do we want a single string to be shared among multiple
interfaces -- especially DPI-C and VPI?

(2) Or do we want to let each interface have its own set
of supported strings?

-------

A separate interesting question is:  Will IEEE let us get
away with referring to previous versions of the standard
within the current version?  That is, dare we specify
the use of strings such as "1364-1995" or "1364-2001"
in a 2008 standard?  Does IEEE have rules against referring
to previous versions, as this may imply that the current
version is not really the sole standard?

Regards,
Jim

--------------------------------------------------------- 
James H. Vellenga                            978-262-6381 
Engineering Director                   (FAX) 978-262-6636 
Cadence Design Systems, Inc.         vellenga@cadence.com 
270 Billerica Rd
Chelmsford, MA 01824-4179
"We all work with partial information." 
----------------------------------------------------------  

]-----Original Message-----
]From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On 
]Behalf Of Stuart Sutherland
]Sent: Monday, January 15, 2007 2:07 PM
]To: sv-cc@eda.org
]Subject: [sv-cc] Change "P1800-2005" in Annex F and G?
]
]
]In the final 1800-2005 standard, Annex F and G still contain 
]references to
]"P1800-2005".  For example:
]
]F.9.1.3 Implementation-dependent representation
]The svDpiVersion() function returns a string indicating which 
]DPI standard
]is supported by the simulator and in particular which canonical value
]representation is being provided. Simulators implementing the current
]standard, i.e., the VPI-based canonical value, must return the string
]"P1800-2005". Simulators implementing to the prior Accellera SV3.1a
]standards, and thus using the svLogicVec32 value representation, shall
]return the string "SV3.1a".
]
]
]After the standard was balloted and approved, the IEEE was supposed to
]change all occurrences of "P1800" to "1800", but they seem to 
]have missed
]these two Annexes.  In the first draft of P1800-2008 that I am 
]currently
]working on, I have changed "P1800-2005" to "1800-2005".  The 
]CC committee
]should discuss this, and make sure this editor-change is OK.  
]If it is, no
]action is needed.
]
]I suggest, however, that either a more generic string be used, 
]such as "IEEE
]1800", or that the next version of the standard return "1800-2008".  If
]either of these changes should be made, then a new Mantis item 
]should be
]created.  If "1800-2008" is used, then the committee might 
]want to leave the
]Mantis item open until just before the next ballot draft, in 
]case 2008 is
]not the ballot year.
]
]Stu
]~~~~~~~~~~~~~~~~~~~~~~~~~
]Stuart Sutherland
]Sutherland HDL, Inc.
]stuart@sutherland-hdl.com
]503-692-0898
]
]
]
]-- 
]This message has been scanned for viruses and
]dangerous content by MailScanner, and is
]believed to be clean.
]
]

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.