Subject: RE: [sv-cc] Updated externexport proposal (version N+2)
From: Joao Geada (Joao.Geada@synopsys.com)
Date: Fri Mar 14 2003 - 15:48:48 PST
Francoise,
Thanks for this answer; I had lost track of the question itself ...
Joao
============================================================================
==
Joao Geada, PhD Principal Engineer Verif Tech
Group
Synopsys, Inc TEL: (508)
263-8083
344 Simarano Drive, Suite 300, FAX: (508)
263-8069
Marlboro, MA 01752, USA
============================================================================
==
-----Original Message-----
From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org]On Behalf Of
Francoise Martinolle
Sent: Friday, March 14, 2003 5:56 PM
To: Michael.Rohleder@motorola.com; Joao.Geada@synopsys.COM
Cc: sv-cc
Subject: Re: [sv-cc] Updated externexport proposal (version N+2)
Michael,
I tried to answer some of your questions.
At 01:56 AM 3/13/2003 +0100, Michael Rohleder wrote:
Joao,
thanks, great work. Here is my feedback from browsing over. Not more I
can do now ...
- I would suggest to remove the NOTE: in paragraph 3 of Semantics
together with issue 2 and put it in our defer bucket for SV 3.2
- Same for issue 3. And b.t.w. I think extends is a solution, not a
workaround
- After reading some feedback from Andrzej, it is unclear to me whether
I now have to call svFetchScope() before I can use any kind of PLI/VPI
function in an external function with context qualifier. I thought (until
now), I can always do this, I only need to retrieve the context, when this
would be needed by the PLI/VPI code. But, as an example io_print() can
always be used ...
You don't not need to get the context with svGetScope for calling a
VPI/PLI function. DPI scope and VPI scope handles are entirely different!
The only reason why we used the qualifier context on the extern declaration
was to tell the SV compiler that this extern function may call VPI or an
exported SV function, therefore it needs to know about its own scope.
....
This archive was generated by hypermail 2b28 : Fri Mar 14 2003 - 15:51:42 PST