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
When using SV interfaces, sv2v likes to produce lots of hierarchical references. Makes sense as it keeps things similar to the original code. However, not all tools fully support hierarchical references.
Quartus seems to have issues with passing hierarchical references to functions, complaining that it can't pass value from actual to argument <x>. A workaround seems to be to define a shadow signal for the signal in question. Not sure if it makes sense to try to work around this specific limitation relating to functions, or if it makes more sense to simply provide an option to avoid generating hierarchical references entirely.
ISE seems to not support hierarchical references at all, or at least it has some issues with the implementation. It returns errors like <signal> is not declared under prefix <entity>.
The text was updated successfully, but these errors were encountered:
When using SV interfaces, sv2v likes to produce lots of hierarchical references. Makes sense as it keeps things similar to the original code. However, not all tools fully support hierarchical references.
Quartus seems to have issues with passing hierarchical references to functions, complaining that it
can't pass value from actual to argument <x>
. A workaround seems to be to define a shadow signal for the signal in question. Not sure if it makes sense to try to work around this specific limitation relating to functions, or if it makes more sense to simply provide an option to avoid generating hierarchical references entirely.ISE seems to not support hierarchical references at all, or at least it has some issues with the implementation. It returns errors like
<signal> is not declared under prefix <entity>
.The text was updated successfully, but these errors were encountered: