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

verilog parser does not accept split-buses in port declaration #275

Closed
veripoolbot opened this issue Aug 2, 2010 · 3 comments
Closed

verilog parser does not accept split-buses in port declaration #275

veripoolbot opened this issue Aug 2, 2010 · 3 comments
Assignees

Comments

@veripoolbot
Copy link
Collaborator


Author Name: Pihay Saelieo
Original Redmine Issue: 275 from https://www.veripool.org
Original Date: 2010-08-02
Original Assignee: Wilson Snyder (@wsnyder)


It looks like the verilog parser does not understand split-bus syntax in the port declaration section of the module header. Our simulation tools, however, can parse this syntax without issues.

For example, the parser will error out when reading the following snippet:

module tb (
OUT1,
{OUT2[1], OUT2[0]}, // Error on this line
IN );
output OUT1;
output [1:0] OUT2;
input [2:0] IN;
endmodule

Attached is a more detailed testcase showing this. Please execute the "read_verilog" script in the same directory as the "sense_q.v" file. The error message is:
%Error: sense_q.v:18: syntax error, unexpected '{', expecting "CLASS-IDENTIFIER" or "COVERGROUP-IDENTIFIER" or "TYPE-IDENTIFIER"

@veripoolbot
Copy link
Collaborator Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2010-08-02T22:42:57Z


I think this is a duplicate of #�, please try the most recent version, which has that fixed.

@veripoolbot
Copy link
Collaborator Author


Original Redmine Comment
Author Name: Pihay Saelieo
Original Date: 2010-08-03T04:20:57Z


Yes, this has indeed been fixed in the most recent version. Sorry for the duplicate bug, and appreciate the help!

@veripoolbot
Copy link
Collaborator Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2010-08-03T11:10:36Z


Great, thanks for the good bug report anyhow!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants