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
Add support for import modport #696
Comments
Original Redmine Comment modport_import makes sense. modport_export makes other simulators upset; I think myfunc needs to be predeclared as an extern. |
Original Redmine Comment Hi Wilson, My bad - I didn't test the export example properly. I've pushed an improved version, which passes with VCS. It does require the extern declaration, which by my reading of the standard should not be necessary. Jeremy |
Original Redmine Comment Modport import is fixed in git towards 3.855. Could you confirm the usefulness of export in synthesized code? Export messes with how linking currently works, so will be a bit of a mess. |
Original Redmine Comment Hi Wilson, Sorry for the slow follow-up over the holiday period. Hope you had a good Christmas and best wishes for 2014. I agree with you on this. I think import is the one that really matters. I found export didn't quite do what I expected with event driven simulation, so just modport_import should be sufficient. That's all the big SystemVerilog test case uses. Jeremy |
Original Redmine Comment Import only then. Resolved with earlier commit. |
Original Redmine Comment In 3.855. |
Author Name: Jeremy Bennett (@jeremybennett)
Original Redmine Issue: 696 from https://www.veripool.org
Original Date: 2013-11-07
Original Assignee: Wilson Snyder (@wsnyder)
This is an enhancement request to add @import@ and @export@ to interface modports.
Please pull simple testcases from branch modport-import-export of https://github.com/jeremybennett/verilator
The text was updated successfully, but these errors were encountered: