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
Accessing parameters by upward-looking hierarchical name seems to always return the value as specified in alphabetically first(!) instance of the module in question.
This is tested with the vlog95 backend; I don't know if it is backend specific.
To test, compile the included example:
iverilog -g2012 -s main -t vlog95 -o inherit.v95 inherit.sv
... and observe the output definition of module "ab".
One would instead expect "main.mybc[01x]"
to have different expansions in their respective instantiations of "ab".
iverilog -v
Icarus Verilog version 12.0 (stable) ()
Files (with .txt added due to github drain bramage):
Accessing parameters by upward-looking hierarchical name seems to always return the value as specified in alphabetically first(!) instance of the module in question.
This is tested with the vlog95 backend; I don't know if it is backend specific.
To test, compile the included example:
iverilog -g2012 -s main -t vlog95 -o inherit.v95 inherit.sv
... and observe the output definition of module "ab".
One would instead expect "main.mybc[01x]"
to have different expansions in their respective instantiations of "ab".
iverilog -v
Icarus Verilog version 12.0 (stable) ()
Files (with .txt added due to github drain bramage):
inherit.sv.txt
inherit.v95.txt
The text was updated successfully, but these errors were encountered: