Subject: [sv-cc] Difference between 'inclusion' proposal and current simulator implementations
From: Michael Rohleder (michael.rohleder@motorola.com)
Date: Tue Feb 18 2003 - 07:19:08 PST
Hi all,
in the course of closing up the 'inclusion issue' w.r.t. to C/C++ code registration (3rd part of the proposal that has been tabled
for 3.2) I thought it might be a good idea to provide some feedback to the major vendors where I (as a dumb user) see the major
differences; especially in light of the proposed 3rd part of the inclusion document. As a reminder, I have attached the actual state
of the proposal; below you'll find the list of differences I see (from an external viewpoint only, it is obvious that there are more
internal differences).
My hope is that this is some first input to solve this issue for the next round (3.2), and should act as a reminder that there is
still something to be done.
This is the last action w.r.t. this topic until we start to work on 3.2; but this does not mean we should forget about it. No time
to get lazy...
Best regards,
Michael
Cadence XL & VCS
. does not support PLI tab file
. NC permits to distinguish between elaboration and simulation registration function; one or both can be specified
. command line invocation is always permitted (XL) - persistent is not required
. minimum, maximum amount of arguments can not be specified
. do only distinguish between task/function, bit and real return values (usertask, userfunction, userrealfunction)
. size_tf can be a function
. call_tf can be given, is optional
. additional parameters in registration function for internal reasons
Synopsys VCS
. does not support vpi_register_systf()
. does not support registration by structure
. does not support loading of shared libraries from the command line
. PLI tab file permits some more options, mostly for optimization
. call_tf must be given
Mentor ModelSim
. does not support PLI tab file
. command line invocation is not possible
. minimum, maximum amount of arguments can not be specified
. do only distinguish between task/function, bit and real return values (usertask, userfunction, userrealfunction)
. size_t can be a function
. call_tf must be given
. additional parameters in registration function for internal reasons
--NOTE: The content of this message may contain personal views which are not neccessarily the views of Motorola, unless specifically stated.
___________________________________________________ | | _ | Michael Rohleder Tel: +49-89-92103-259 | _ / )| Software Technologist Fax: +49-89-92103-680 |( \ / / | Motorola, Semiconductor Products, System Design | \ \ _( (_ | _ Schatzbogen 7, D-81829 Munich, Germany _ | _) )_ (((\ \>|_/ > < \_|</ /))) (\\\\ \_/ / mailto:Michael.Rohleder@motorola.com \ \_/ ////) \ /_______________________________________________\ / \ _/ \_ / / / \ \
The information contained in this email has been classified as: Motorola General Business Information (x) Motorola Internal Use Only ( ) Motorola Confidential Proprietary ( )
*** This note may contain Motorola Confidential Proprietary or Motorola Internal Use Only Information and is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. Thank you! ***
This archive was generated by hypermail 2b28 : Tue Feb 18 2003 - 07:19:57 PST