Subject: [sv-cc] meeting minutes 3/4
From: Francoise Martinolle (fm@cadence.com)
Date: Tue Mar 04 2003 - 10:01:16 PST
meeting minutes from last week
? proposed.
joao seconded
at the chairs meeting, vassilios gave a roadmap for the schedule.
technology freeze next week
LRM editing complete by end of March
Let's meet on wednesday to go over the small items
Joao has all the source for the documents. Joe is off the project as of
this friday.
Ghassan is trying to find some stand-by editor and everything will go to
stuart at the end.
All caps for all #defines accepted anonymously
supporting references in DPI: rejected.
references are added so that you don't have to do copy in and out.
All against supporting references except Kevin.
Kevin's comment: it is useful for passing PLI handles
Joao: extern/export
import and export recommended by EC
import bring a C function
export: make a SV function available to C
Francoise: import/export is confusing and not the same usage as in the modport
Kevin: there are also the extern modules
Andrezj: 2 issues: avoid syntactical ambiguity
esthetic issue
Issue: Scopes for import and export declarations
import can be in the scope where you want to use it.
Any scope for exported function
Andrzej prefers:
import extern
export extern.
Where do we allow the export/import?
context sensitive calls reusable models which use VPI
function to create a context, some notion of the hierarchy is stored somewhere.
if a module is instanted twice, the export is instantiated, the function
definition is also instantiated
SV to C call, default context is current instance
John: Every call form C to SV would have to be preceded by a set_context.
Joao: SV to C call uses the default context, C calls SV. Large use is to
not manipulate the context.
Michael: I can see the runtime benefit in passing a context pointer.
Joao: a 3rd function is needed: get a context from a name
Doug: argument symmetry is broken between C and SV if we add a context argument
Francoise: Need to send the latest document for refresh
Doug: will update the document
Joao summarized the issues:
syntax,
scope of the declarations
semantic: one import or one export per scope
signature : type exactly the same except for open arrays
arguments in same order
no name or no default value
export with prototype was only needed because the export was not in the
same scope
as the function definition.
SV-AC has some feedback about the assertion API.
Joao needs to comment on it.
Joao agrees on the comments and will change the document.
Add one more directive
Bassam: these are the only comments from the SV-AC
Schedule a temptative vote by this Friday.
Attendees:
John Amouroux
John Stickley
bassam,
andrzej
Francoise
joao,
kevin
Joe Daniels,
Swapnajit
Doug
Michael
This archive was generated by hypermail 2b28 : Tue Mar 04 2003 - 10:01:59 PST