We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Author Name: Julien Margetts Original Redmine Issue: 1330 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
This internal error occurs when verilating the attached test case, but only when the --trace switch is specified
verilator -cc --exe <attachedfile.v> --trace
Additional infomation from --debug switch:
%Error: Internal Error: cache.v:26: ../V3Broken.cpp:224: Broken link in node (or something without maybePointedTo): m_taskp && !m_taskp->brokeExists()
The text was updated successfully, but these errors were encountered:
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2018-08-21T22:09:53Z
Thanks for the good test case, this was related to certain function calls under while loops.
Fixed in git towards 3.925.
Sorry, something went wrong.
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2018-08-22T22:48:33Z
In 3.926.
wsnyder
No branches or pull requests
Author Name: Julien Margetts
Original Redmine Issue: 1330 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
This internal error occurs when verilating the attached test case, but only when the --trace switch is specified
verilator -cc --exe <attachedfile.v> --trace
Additional infomation from --debug switch:
%Error: Internal Error: cache.v:26: ../V3Broken.cpp:224: Broken link in node (or something without maybePointedTo): m_taskp && !m_taskp->brokeExists()
The text was updated successfully, but these errors were encountered: