Subject: $sv-ec SV APIs (Assertion)
From: Kevin Cameron (Kevin.Cameron@nsc.com)
Date: Tue Oct 01 2002 - 10:22:46 PDT
Since a lot of C and C++ functionality has been (or is being) pulled into the SV
language, it seems less important to me that we add new APIs. Most C/C++
code could probably be translated into SV and probably would compile more
efficiently (since it wouldn't have to go through an API).
IMO we should concentrate on low-level cross-calling mechanisms (calling
C directly from SV, and C back into SV via tasks and functions), so that
it is easy to link libraries of SV and C/C++ code.
WRT to the assertion API, it would make more sense to me to implement the
control functions (enable, diasble, reset etc.) in SV and to do call-backs as regular
events in SV, e.g.
@(<assertion name>) ....
Since the Testbench donation adds new event types beyond the Verilog "one-shot"
that mechanism should handle all the assertion states.
The Assertion API requirements should be passed on to the AC committee for
inclusion in the SV language proper.
Regards,
Kev.
This archive was generated by hypermail 2b28 : Tue Oct 01 2002 - 10:24:24 PDT