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

how to ignore the warning? #1073

Closed
veripoolbot opened this issue Jul 12, 2016 · 5 comments
Closed

how to ignore the warning? #1073

veripoolbot opened this issue Jul 12, 2016 · 5 comments
Labels
resolution: no fix needed Closed; no fix required (not a bug)

Comments

@veripoolbot
Copy link
Contributor


Author Name: nan wu
Original Redmine Issue: 1073 from https://www.veripool.org
Original Date: 2016-07-12


I am a new user. There will be warnings and error When there is a delay(such as '#10') in the verilog module. It shows" Warning-STMTDLY: Use "/* verilator lint_off STMTDLY */" and lint_on around source to disable this message. "
So I added "lint_off -msg STMTDLY" in file named t_vlt_warn.vlt. But it didn't work.
Please help me !
Thanks very much!

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Jie Xu (@jiexu)
Original Date: 2016-07-12T07:20:57Z


Generally two ways to disable warning.

You can add some comments in the verilog source where the warning is reported, then the particular warning will be ignored.

/* verilator lint_off STMTDLY */
ssdfd  // code where the warning is report
/* verilator lint_on STMTDLY */

Another way is to disable all STMTDLY warning by adding

-Wno-STMTDLY

option when you invoke Verilator.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: nan wu
Original Date: 2016-07-12T08:16:27Z


%Warning-STMTDLY: our.v:20: Unsupported: Ignoring delay on this delayed statement.

The problem is solved, but I found that the delay(such as "#10") has been optimized and ignored. It didn't work.
How to make it not ignore the delay ?

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Jie Xu (@jiexu)
Original Date: 2016-07-12T09:50:07Z


Short answer: you can't.

Long answer: Verilator simulates synthesizable verilog code and @#10@ is not synthesizable.

Please read a bit more about documentation.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: nan wu
Original Date: 2016-07-12T13:00:17Z


I am sorry. I have saw that Verilator simulates synthesizable verilog code in documentation. But there still is a foolish question in my mind--how to simulate(provide input)? We write testbench by verilogHDL when using ModelSim, does it need use SystemC/C++ to create the testbench if we use Verilator? Then the testbench will be very complex in order to test all the situations, but the authority said it just need write a touch of C code and Makefiles after synthesizable verilog is migrated to C++ or SystemC.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2016-07-14T02:52:33Z


No change needed. See also the errors and warnings section of the manual, to which I made a tweak in git to mention config files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: no fix needed Closed; no fix required (not a bug)
Projects
None yet
Development

No branches or pull requests

1 participant