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

Tracking: Parameter-Controlled Bind Statements in Verilator #639

Open
drichmond opened this issue Mar 28, 2022 · 1 comment
Open

Tracking: Parameter-Controlled Bind Statements in Verilator #639

drichmond opened this issue Mar 28, 2022 · 1 comment
Assignees

Comments

@drichmond
Copy link
Contributor

Filing this for tracking, and so we can link it to the Verilator issue we will file.

In #636, we added several lines that clock gate the parameter-controlled bind statements in Verilator. This is because Verilator seems to instantiate this modules, even when the parameters supposedly prevent their instantiation.

They look roughly like this:

,.clk_i(clk_i && $root.`HOST_MODULE_PATH.testbench.enable_vcore_profiling_p)

Similar statements exist for enable_cache_profiling_p enable_router_profiling_p enable_vcore_pc_coverage_p and enable_vanilla_core_trace_p.

When this bug is fixed in Verilator, we need to undo this change and revert back to the original source.

@dpetrisko
Copy link
Contributor

Found the issue, it got ported over from their old issue tracker: verilator/verilator#1501

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

No branches or pull requests

2 participants