Subject: [sv-cc] Minutes 02-25-2003
From: Joao Geada (Joao.Geada@synopsys.com)
Date: Tue Feb 25 2003 - 10:14:01 PST
Attendees:
Michael
Joao
Ghassan
Andrzej
Joe Daniels
Francoise
John Stickley
Bassam
- minutes from last meeting approved (Joao proposed, Joe seconded)
- discussion on the linking (Michael's proposal) poll underway
* it is a line item vote (part 1 and part 2)
* confirmation that voting deadline extended to end of today (2/25/03)
- LRM update (Joe)
* there are 6 parts to sv-cc LRM contribution
* discussion underway on how sv-cc LRM components will be part of a separate volume of
the SV 3.1 LRM
* there will be 3 chapters:
SV interface (VPI extensions)
Assertion API
Coverage API
"DirectC" API
SV language layer
C layer
include files for interface
Michael's foreign linking proposal
* 60+ pages of documentation, forecasts reaching 80 pages at end
* assertion API basically completed
* coverage API first draft written, being reviewed
* C layer and include files draft written, being reviewed
* Michael's foreign linking proposal pending voting
- Michael brought up point that we need to have some discussion on an alternate
name for the DirectC interface (Accellera rules require a different name)
- Chairs have been exchanging the LRM documents as they have been produced
- Ghassan asked that everyone that is feeding information to Joe to give that
feedback ASAP
- Joao discussed issues with extern/export SV layer
* syntax conflicts and/or possible user confusion related to SV 3.1 existing
usages of extern/export/import and presence of prototypes
* issues arising with exports and use of Verilog libraries
* Joao to make first cut syntax proposal by tomorrow
* Joe to send current state of SV layer draft
- discussion on foreign code linking
- part 1 - object linking, part 2 - foreign source inclusion
- Andrzej issues:
* only recommendations rather than requirements
* forcing specific command line switch naming
* Michael says that command line arguments are recommendations
* it is the *semantics* of switch that is important, not name
* shared library linking only
* discussion on merits of shared library linking vs plain objects and libraries
* dlopen is POSIX (Joao had questions regarding this, but google lookup confirmed)
* VCS can handle all kinds of linking and prefers compile time linking, whereas most
other simulators prefer runtime shared library linking
* transitivity of linking (both library a and library b requires function b, which requires library c)
* Michael states that this is a "user-space" problem, not resolvable in context of this proposal
* John: are we trying to standardize on how things are linked or something else ?
- argument passing and default arguments
* calling SV from C cannot have pass by name or default values. All parameters must be supplied
* from SV calling C, no issues as SV compiler can provide all the arguments by expanding defaults
and remapping passing-by-name to canonical argument order
* read through Andrzej's passing by name and default handling proposal
Francoise: does this apply to all functions (native and C) or just C
Andrzej: only C functions. Do not need (and cannot) change native function behavior
Francoise: would prefer to have consistent definition for all functions
Andrzej: cannot be consistent because definition missing for C functions and because
C functions may have multiple (non-conflicting) declarations with different
names used for arguments
Michael: needs description on how default arguments handled in passing by position
Andrzej: (consistent with native function invocation)
Joao: is it viable to restrict to a single extern ?
Michael (et al): NO!
all: Andrzej's current proposal is pretty good now
- some naming brainstorming
Michael presented that we produced a number of SV C(foreign language) interfaces,
including VPI extensions and the "DirectC" interface.
Various names discussed (refer to Michael's email)
(since I wrote the minutes, I get to have the last word:
* I like SV API for the general framework, containing
assertion VPI extensions
coverage VPI extensions
DPI (Direct Programming Interface)
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
==============================================================================
This archive was generated by hypermail 2b28 : Tue Feb 25 2003 - 10:15:44 PST