[sv-cc] Revision 4 of DPI task proposal


Subject: [sv-cc] Revision 4 of DPI task proposal
From: Warmke, Doug (doug_warmke@mentorg.com)
Date: Fri Nov 07 2003 - 23:23:24 PST


Swapnajit, team,

Here is the next revision of our DPI task proposal (#4).
It contains all feedback I've heard over the course of
the last month.

Changes include:
1) It is now legal for an exported function to disable
   a calling import task, or a tf higher up the call chain.
   New API svIsDisabledState() is added for this purpose.
2) New API svAckDisabledState() has been added in order that
   imported functions can follow the disable protocol by
   positively acknowledging their disable status.
3) Return values of either 0 or 1 are mandatory for
   imported tasks. (Michael's request that all other values
   be explicitly barred)
4) A complete description of the disable protocol is given.
5) Clarifications have been made about the update of function
   return values and tf output and inout parameters during
   disable processing. (Basically such values are undefined,
   which matches native tf behavior during disable processing).
6) It is explicitly disallowed to propagate a C++ exception
   out of DPI import code and into the SystemVerilog simulator.
7) It is mentioned that DPI C programmers must take care of
   re-entrancy concerns when programming imported tasks.

I look forward to making progress on this technology during
our face to face meeting next week.

Thanks and regards,
Doug




This archive was generated by hypermail 2b28 : Fri Nov 07 2003 - 23:25:40 PST