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

Multi Threading Programming Support in Verilator #853

Closed
veripoolbot opened this issue Nov 28, 2014 · 2 comments
Closed

Multi Threading Programming Support in Verilator #853

veripoolbot opened this issue Nov 28, 2014 · 2 comments
Labels
area: usability Issue involves general usability resolution: no fix needed Closed; no fix required (not a bug)

Comments

@veripoolbot
Copy link
Contributor


Author Name: Prateek Puri
Original Redmine Issue: 853 from https://www.veripool.org
Original Date: 2014-11-28


Hi

This might be a dumb question.
I have written a test bench in C++ for verilated code which uses thread library (c++11). I am not finding any way to compile this using Verilator.
I can use pthread.h if required but that also require certain flags.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2014-11-28T16:47:20Z


Thanks for the bug. Please say exactly what errors you are getting and how to recreate the problem.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2014-11-28T17:57:33Z


I think you were looking for
$VERILATOR_BIN/bin/verilator -Wall --cc -CFLAGS '-std=gnu++0x' -LDFLAGS '-lpthread' --trace b12.v --exe b12_cpp_tb.cpp

@veripoolbot veripoolbot added area: usability Issue involves general usability resolution: nofixneeded resolution: no fix needed Closed; no fix required (not a bug) and removed resolution: nofixneeded labels Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: usability Issue involves general usability resolution: no fix needed Closed; no fix required (not a bug)
Projects
None yet
Development

No branches or pull requests

1 participant