-
Notifications
You must be signed in to change notification settings - Fork 50
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
VCS backend fails on blocks with no IOs (standalone) #153
Comments
Is this actually legal according to the Verilog spec--i.e., is VCS wrong, or is Verilator too lax? |
I don't see any trailing commas allowed in the Verilog 2001 module instantiation spec, unless the thing called "expression" is allowed to be empty. But if it was, then there would be three parameters to module and they are only two where to module is defined. Fixing this should be easy---it is not as if verilator is going to fail if we remove the extra comma. |
Yeah, of course. I asked because I was going to file a ticket if it was a VCS bug. |
I think it's because verilator and FIRRTL tests don't generate a Verilog test harness. Only VCS does. |
The code below fails to compile in VCS but works with Verilator and firrtl-interpreter.
The trailing comma after the reset binding in the harness is the issue:
The text was updated successfully, but these errors were encountered: