RE: [sv-bc] 1800-2009 H.10.1.3 svDpiVersion on 2009 simulators (SV)

Hi,

This was discussed several times in the past.

See the threads beginning with the following:

http://www.eda.org/sv-cc/hm/3179.html
http://www.eda.org/sv-cc/hm/3474.html
http://www.eda.org/sv-cc/hm/3877.html
http://www.eda.org/sv-cc/hm/3969.html

It seems there was not enough sentiment to change this.

Shalom

> -----Original Message-----
> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On
> Behalf Of Neil Korpusik
> Sent: Thursday, January 28, 2010 3:14 AM
> To: Wilson Snyder; SV-CC
> Cc: sv-bc@eda.org
> Subject: Re: [sv-bc] 1800-2009 H.10.1.3 svDpiVersion on 2009
> simulators (SV)
>
> <forwarding to the sv-cc, where the DPI issues are handled>
>
> On 01/27/10 17:05, Wilson Snyder wrote:
> > 1800-2009 H.10.1.3 states:
> >
> > "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. For example, a tool that is based on IEEE Std
> > 1800-2005, i.e., the VPI-based canonical value, shall return
> > the string "1800-2005". Simulators implementing to the prior
> > Accellera SV3.1a standards, and thus using the svLogicVec32
> > value representa- tion, shall return the string "SV3.1a".
> >
> > /* Returns either version string "1800-2005" or "SV3.1a" */
> > const char* svDpiVersion();
> >
> > I'd like to confirm if "1800-2005" is indeed correct for a
> > 1800-2009 simulator, since this refers also to the VPI which
> > does have differences for 1800-2009?
> >
> > I found mantis bug 2101 reporting a similar issue, however
> > this issue was not resolved either way, nor included in the
> > 2009 document. It would be good if the resolution could be
> > reflected there.
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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