We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Author Name: alberto castella Original Redmine Issue: 1118 from https://www.veripool.org
I am writing some system verilog testbench. However, when I create a clocking block, I obtain the following error
@
default clocking cl @(posedge clk); default input #100ps output #100ps; output rst_n; output start; output mode; output K; output init_delay; output middle_delay; output end_delay; input addr; input addr_en; input dones; endclocking
@ syntax error, unexpected IDENTIFIER, expecting '@'.
How can I solve it?
The text was updated successfully, but these errors were encountered:
Original Redmine Comment Author Name: alberto castella Original Date: 2016-12-07T16:33:14Z
Sorry, here is the code
Sorry, something went wrong.
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2016-12-08T12:25:01Z
Verilator does not support SystemVerilog verification constructs, sorry.
If everything works except this, and you'd like to make a patch to support this, please reopen and we can discuss how to go about that.
No branches or pull requests
Author Name: alberto castella
Original Redmine Issue: 1118 from https://www.veripool.org
I am writing some system verilog testbench. However, when I create a clocking block, I obtain the following error
@
default clocking cl @(posedge clk);
default input #100ps output #100ps;
output rst_n;
output start;
output mode;
output K;
output init_delay;
output middle_delay;
output end_delay;
input addr;
input addr_en;
input dones;
endclocking
@
syntax error, unexpected IDENTIFIER, expecting '@'.
How can I solve it?
The text was updated successfully, but these errors were encountered: