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
Broken node on indexed interface modport #1430
Comments
Original Redmine Comment The line before "Internal Error" should have been an error about node 66ade10
4#> {gl75} s_cut -> IFACE 0x5fd0a90 {m20} AXI_BUS__A40_AB40_AC5_AD1 L7 [LIB] Somehow processing has lost AXI_BUS__A40_AB40_AC5_AD1. Can you make a test case? |
Original Redmine Comment If the entire (preprocessed) design is acceptable as a testcase, please find it attached. |
Original Redmine Comment What command line are you using? Can you please check with the most recent version? If that fails, a reduced test case would be appreciated, as would like something we can add to the regressions. |
Original Redmine Comment The usual command line, as stated in the attached logfile: verilator -cc --top-module ariane_testharness --debug --gdbbt verilate-tokens.v is sufficient to demonstrate the problem. Since I'm not particularly familiar with your code it could be difficult to dissect further. Nevertheless since it is pre-processed open source code, I see no reason why it could not go in the regression suite, once the problem is reproduced and identified at your end. I have rerun with the latest release (Verilator 4.012 2019-03-23) with no obvious change in behaviour. If you want me to rerun with any other flags, I'm happy to do so, but to a non C++ developer the diagnostics don't mean a lot. |
Original Redmine Comment Tracked this down to an issue that indexed interfaces with modports are broken in LinkDot. Stay tuned. |
I believe I have also hit this bug now in a separate project from the original report. Verilator 4.032 reports the below log when running verilato_bin_dbg under gdb with --debug --gdbbt. I had been using arrays of interfaces with modports within the design without encountering a problem, but after adding in a crossbar implementation that heavily uses indexed 1D arrays of interfaces the problem cropped up. Based on the previous comment I removed all the modports from the design, leaving just the interfaces, but the issue persisted. If this looks to be a separate issue I can also file separately and attempt to distill a testcase.
|
@engr248 I think it's unlikely this is the same issue, please file a new bug with a small test case. If you run with "--debug --gdb" when you get the prompt, type
and this should show you the filename and pin causing the issue. |
Never got test case and other fixes that might have fixed this - if this is still a problem please open a new issue, thanks. |
Author Name: Jonathan Kimmitt (@jrrk2)
Original Redmine Issue: 1430 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
The text was updated successfully, but these errors were encountered: