Skip to content

Special verilog parameters tb_path and output_path don't work in Riviera-PRO#683

Open
pib88 wants to merge 1 commit intoVUnit:masterfrom
pib88:fix_special_generics_issue
Open

Special verilog parameters tb_path and output_path don't work in Riviera-PRO#683
pib88 wants to merge 1 commit intoVUnit:masterfrom
pib88:fix_special_generics_issue

Conversation

@pib88
Copy link
Contributor

@pib88 pib88 commented Sep 29, 2020

When you use tb_path or output_path in verilog they are specified in command line like this:
-gtb_path=<TB_PATH>

That does not work in Riviera because you need to put string in double quotes to have it interpreted correctly:
-gtb_path="<TB_PATH>"

Since it's impossible to determine parameter type by its value, solution should be limited to parameters that we know are strings: tb_path and output_path.

@dalex78
Copy link
Contributor

dalex78 commented May 10, 2022

It look good to me, however, I do not have Riviera and cannot confirm the issue or the proposed fix. But I do not see any issue with the code.
@LarsAsplund, I suggest to merge.

@eine eine added this to the v4.7.0 milestone May 11, 2022
@eine eine force-pushed the fix_special_generics_issue branch 2 times, most recently from f108a2a to ed48a9e Compare May 11, 2022 23:56
Special string parameters like tb_path and output_path should be in quotes when used in verilog
@eine eine force-pushed the fix_special_generics_issue branch from ed48a9e to 402bd1e Compare May 11, 2022 23:58
@eine eine modified the milestones: v4.7.0, v4.8.0, v5.0.0 Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants