You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if ((port.transparency_mask[j] || port.collision_x_mask[j]) && !wport.removed) {
log_assert(port.clk_enable);
This is when trying to convert some VHDL->Verilog (using ghdl plugin front end)
I think it has to do with how the HDL describes a dual port ram? (does successfully map to Xilinx BRAMs)
I did indeed forget that GHDL alone can convert to Verilog! I will absolutely try this ✊
However, I feel like I once heard that the path through Yosys is generally 'better' for producing verilog - without details on what that means? I suppose we'll see 🤓
Description
I am hitting this assertion and erroring out
https://github.com/YosysHQ/yosys/blob/41b34a19353dbbe00aa08f3561e25e0bfa4c84d2/kernel/mem.cc#L473C5-L473C33
This is when trying to convert some VHDL->Verilog (using ghdl plugin front end)
I think it has to do with how the HDL describes a dual port ram? (does successfully map to Xilinx BRAMs)
Expected behaviour
No assertion error.
How to reproduce?
convert_to_verilog.sh:
output snippet:
Context
GHDL 4.0.0-dev (3.0.0.r448.g2245a7fd1) [Dunoon edition]
Yosys 0.32+76 (git sha1 73cb4977b, clang 10.0.0-4ubuntu1 -fPIC -Os)
Yosys dev said this is an issue with how GHDL is emitting the RAM... 🤷
Does this have to do with the relaxed-to-warning
shared variable must be a protected type
error?Thanks for your time
ram_error.zip
The text was updated successfully, but these errors were encountered: