Skip to content
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

DPI problem with vector task arguments #347

Closed
veripoolbot opened this issue May 10, 2011 · 4 comments
Closed

DPI problem with vector task arguments #347

veripoolbot opened this issue May 10, 2011 · 4 comments
Assignees
Labels
resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor


Author Name: Chandan Egbert
Original Redmine Issue: 347 from https://www.veripool.org
Original Date: 2011-05-10
Original Assignee: Wilson Snyder (@wsnyder)


Verilator version: Verilator 3.812 2011/04/06 rev verilator_3_811-18-ga20b4f2

When a task with vector input arguments is exported as a DPI call, gcc fails with the complaint

error: invalid operands of types 'int' and 'const svBitVecVal*' to binary 'operator&'

when compiling V__ALLcls.cpp. The problem is that the argument is passed by reference, but not dereferenced before assignment. Run the example with "sh doit.sh" to see the problem.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Chandan Egbert
Original Date: 2011-05-10T20:40:59Z


Attached is the example and a patch that fixes the problem

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2011-05-12T11:35:53Z


Your patch was close; it only needed to be done on bit vector types not non-vector types.

Fixed in git for 3.813.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2011-06-29T00:56:48Z


In 3.813.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2011-06-29T00:57:06Z


In 3.813.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: fixed Closed; fixed
Projects
None yet
Development

No branches or pull requests

2 participants