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

scr1 test suite: delayed always blocks are unsupported #1291

Closed
veripoolbot opened this issue Mar 10, 2018 · 2 comments
Closed

scr1 test suite: delayed always blocks are unsupported #1291

veripoolbot opened this issue Mar 10, 2018 · 2 comments

Comments

@veripoolbot
Copy link

@veripoolbot veripoolbot commented Mar 10, 2018


Author Name: Joel Holdsworth
Original Redmine Issue: 1291 from https://www.veripool.org


This code generates a warning:

module test();               

reg clk = 0;                 
always #123 clk = !clk;      

endmodule

%Warning-STMTDLY: Use "/* verilator lint_off STMTDLY */" and lint_on around source to disable this message.            
%Error: Exiting due to 1 warning(s)                        
%Error: See the manual and http://www.veripool.org/verilator for more assistance.                                      
%Error: Command Failed /usr/local/bin/verilator_bin -sv --lint-only test_always_delay.sv

Would it be possible to support delayed always blocks that lack sensitivity lists?

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Mar 10, 2018


Original Redmine Comment
Author Name: Joel Holdsworth
Original Date: 2018-03-10T16:16:58Z


RTFM.... I see this isn't going to work

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Mar 10, 2018


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2018-03-10T17:50:40Z


Correct, clocks must come from the C side. At least until events are supported which is long off.

Note you can turn off the warning but that won't help the intent of this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.