SCE-MI 2 DPI data type support for "old Verilog"

Greetings ITC Techies,

As per my AI, here is a small pros/cons listing of the
3 approaches we discussed for DPI data type support for
old Verilog. Please feel free to add if I've missed
anything.

Option 1:
   Support all three languages with full data type support

   pros:
     User C models will be binary compatible for all
     supported SCE-MI 2 data types regardess of what
     language is used on HDL side

   cons:
     Uses awkward attributing scheme to specify additional
     old Verilog integer types than what the language natively
     supports

Option 2:
   Support only limited native types in Verilog, but full
   SCE-MI 2 DPI data type subset set for SystemVerilog, VHDL

   pros:
     No special attributing scheme required for old Verilog
     (other than import/export declaration attribute/pragma
     itself - this would still be required)

   cons:
     Only C models limited to using basic int and 2 state bit
     vector types will work across all 3 languages

Option 3:
   Support SystemVerilog, VHDL only, no Verilog

   pros:
     Don't have to deal with old Verilog's limitations -
     especially given that the big 3 vendors will have basic
     SystemVerilog DPI support anyway. Even smaller vendors
     can possibly create extensions to their Verilog parsers to add
     limited SystemVerilog DPI support (as per SCE-MI 2 subset)

   cons:
     Legacy "old Verilog" platforms will not be supported.

-- johnS


______________________________/\/            \     \
John Stickley                   \             \     \
Mgr., Acceleration Methodologies \             \________________
________________________________________________________________