New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
../V3Ast.cpp:481: Node has no back, already unlinked? -- interfaces, modport, unpacked array badness #1135
Comments
Original Redmine Comment Thanks for the test. Fixed in git towards 3.902. |
Original Redmine Comment Wilson Snyder wrote:
This change breaks all our designs. I haven't been able to debug why yet except that it crashes in V3Inline.cpp:518, pinNewVarp is NULL. |
Original Redmine Comment Reopening... Johan, if you can please make an example or patch, as it's not obvious why the previous clone failed. BTW at V3Inline.cpp line 513 I added in trunk: but obviously that just makes a slightly nicer message rather than fixing anything. |
Original Redmine Comment Wilson Snyder wrote:
Curiously enough our code that was pretty much identical to the example John posted.
|
Original Redmine Comment Johan Bjork wrote:
Attached patch. |
Original Redmine Comment Great, thanks, patch pushed. Let's give this another try. |
Original Redmine Comment In 3.902. |
Author Name: John (Pete) Stevenson
Original Redmine Issue: 1135 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
The attached code works fine with one mux instantiated, but with two muxes instantiated it emits a strange error message:
The issue might be a bad interaction between interfaces, modports, and unpacked arrays.
Using the attached 5 files, command line and stdout:
Testbench.sv:
Thinker.sv:
ThingMuxOH.sv:
the_intf.sv:
pkg.sv:
The text was updated successfully, but these errors were encountered: