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: Shinobu TAKANASHI Original Redmine Issue: 1198 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
Hi,
I'd worked for 2 days to find out the way to "access signals in C" and noticed the document was wrong (for recent version of Verilator).
The following
cout << "clock is " << top->v->clk << endl; </code>
should be like bellow, right?
cout << "clock is " << top->our->clk << endl; </code>
I was just lucky I could find the clue: openrisc/orpsoc-cores#111
Hope this will be fixed.
Thanks
The text was updated successfully, but these errors were encountered:
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2017-09-07T00:46:36Z
Thanks for the feedback. Docs updated in git towards 3.909.
Sorry, something went wrong.
wsnyder
No branches or pull requests
Author Name: Shinobu TAKANASHI
Original Redmine Issue: 1198 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
Hi,
I'd worked for 2 days to find out the way to "access signals in C" and noticed the document was wrong (for recent version of Verilator).
The following
should be like bellow, right?
I was just lucky I could find the clue:
openrisc/orpsoc-cores#111
Hope this will be fixed.
Thanks
The text was updated successfully, but these errors were encountered: