Verilog future?

[ktbarrett]

Hi, I noticed you recently started working on Verilog support and wondered what the end goal of this project is. Just sufficient (System)Verilog support to cover most synthesizable code, like what Icarus hopes to be. Or will it try to cover all of SV to support things like UVM?

What's the status of the VPI? Is it stable enough to start testing?

[nickg]

Hi, I noticed you recently started working on Verilog support and wondered what the end goal of this project is. Just sufficient (System)Verilog support to cover most synthesizable code, like what Icarus hopes to be. Or will it try to cover all of SV to support things like UVM?

The original use case was simulating bits of Verilog vendor IP in an otherwise VHDL design (e.g. #1227 or #1207). I'm slowly making the backend more Verilog-aware (e.g. it now has active/inactive/NBA scheduling regions so Verilog testbenches that rely on this should work properly) and I'm not opposed to adding more SV features but realistically it's going to be a while before it supports everything required for UVM.

What's the status of the VPI? Is it stable enough to start testing?

There's a very minimal VPI implementation but at the moment it's just there to implement system tasks like $display, $finish, and so on. The symbols aren't exported and there isn't enough to run cocotb yet.

[ktbarrett]

I figured it was for vendor IP compat. But being the first (AFAIK) mixed language simulator is a draw that I'm sure many people will be interested in.

Have you considered using an existing Verilog parser such as slang?

The symbols aren't exported and there isn't enough to run cocotb yet.

Gotcha. I may bother you again in the future, if this does become a thing, to maybe directly support GPI instead of having to navigate mixed language support between VPI and VHPI.

[Blebowski]

Hi @ktbarrett,

sorry for jumping in, I was asking something similar some time ago, maybe this gives you some answers:
#650

[ktbarrett]

Thanks for the additional context.

[nohous]

just a quick question, wouldn't the slang SV frontend be useful here or is the architecture just too far away?