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: Dan Kirkham Original Redmine Issue: 1308 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
This syntax error took me a while to figure out because verilator crashes with no useful error output.
//module param_list_no_hash #( // Correct syntax FOO=1 ) ( output bar ); assign bar = FOO; endmodule
/usr/local/bin/verilator_bin_dbg -cc module.v --debug Starting Verilator 3.922 2018-03-17 rev UNKNOWN_REV - V3Os.cpp:57: export SYSTEMC_ARCH=cygwin # From sysname 'cygwin_nt-10.0' - V3File.cpp:205: --check-times failed: no input obj_dir/Vmodule__verFiles.dat - V3GraphTest.cpp:356:selfTest: - V3ParseImp.cpp:97: parseFile: module Preprocessing module.v - V3PreShell.cpp:137: Reading module.v - V3ParseImp.cpp:164: Lexing module.v %Error: export VERILATOR_ROOT= %Error: /usr/local/bin/verilator_bin_dbg -cc module.v --debug %Error: Command Failed /usr/local/bin/verilator_bin_dbg -cc module.v --debug </pre
The text was updated successfully, but these errors were encountered:
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2018-05-09T22:32:31Z
Thanks for the test case; simple enough to solve.
Fixed in git towards 3.924.
Sorry, something went wrong.
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2018-06-13T01:29:06Z
In 3.924.
wsnyder
No branches or pull requests
Author Name: Dan Kirkham
Original Redmine Issue: 1308 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
This syntax error took me a while to figure out because verilator crashes with no useful error output.
The text was updated successfully, but these errors were encountered: