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
vpi_get of vpiSize property broken #680
Comments
Original Redmine Comment Fix on branch vpi-vpiSize-680 at https://github.com/rporter/verilator, but test case fails due to #681. |
Original Redmine Comment Big patch! Some mostly minor stuff:
|
Original Redmine Comment
Mostly it's a merge from the vpi-memory branch of commits that didn't make into the previous patch. These were mainly to do with supporting Icarus, that's most of the deltas there. But I botched conflicts in the merge and ended up changing the rangep back to range because of sloppy checking on my part. Ditto white space. Sorry about that. I've made some changes and a I've added the header as TestSimulator.h. Accessors const'ed. $stop to $finish was an Icarus thing. It falls back to the command line on $stop, but I have subsequently found a "don't fall back to command line on $stop" switch so have reverted them.
|
Original Redmine Comment I've removed the port checks for verilator in The vpi-vpiSize-680 branch diff looks ok now, but There's also a small conflict in |
Original Redmine Comment Pushed to git towards 3.854. Thanks for the great work (again!). I took the liberty of making a few minor changes to TestSimulator.h, I made it a static class so all of the instance() calls weren't needed, made accessors for each simulator, made it work for VCS, and also added TestVpi.h. |
Original Redmine Comment In 3.854. |
Author Name: Rich Porter
Original Redmine Issue: 680 from https://www.veripool.org
Original Date: 2013-09-27
Original Assignee: Rich Porter
vpi_get(vpiSize, regHandle) always returns zero. The existing test case only checks memories and memory words, not regular reg's.
I'll create a new test case and a patch.
The text was updated successfully, but these errors were encountered: