Stats

  • Locked Locked
  • Replies 5
  • Subscribers 64
  • Views 15743
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DPI which can talk C++

archive

Hi,

AT this moment the System Verilog standard only defines a DPI layer for C. I believe there is lot of code out there which may need a C++ DPI wherein C++ and Systemverilog can talk in terms of object rather than simple data types.

I was wondering how people are handling this issue?

One of the methods could be to provide C methods to query C++ data structures. The problem with this method is that either you have to define global objects in C++ part of your code (or static members) or you can only work with the C++ objects with the C function being called from SystemVerilog.

Thanks,
Nitin


Originally posted in cdnusers.org by nitin_sharma
Parents

  • Hi Nitin,
    Was equally frustrated with these issues when i experimented with DPI early this year. Did "google" and found a few techniques that that SV LRM talks about. Read the section on "scope".  Eventhough the LRM talks about these mechanism, mangling in C++ was a problem and hence I gave up.

    I reseorted to your last option.
    "c++ objects with the C function being called from SystemVerilog"
    Regards,
    Ravi

    P.S. There are some papers sitting out there that may interest you.


    Originally posted in cdnusers.org by venravi
Reply

  • Hi Nitin,
    Was equally frustrated with these issues when i experimented with DPI early this year. Did "google" and found a few techniques that that SV LRM talks about. Read the section on "scope".  Eventhough the LRM talks about these mechanism, mangling in C++ was a problem and hence I gave up.

    I reseorted to your last option.
    "c++ objects with the C function being called from SystemVerilog"
    Regards,
    Ravi

    P.S. There are some papers sitting out there that may interest you.


    Originally posted in cdnusers.org by venravi
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.