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

Jump to bottom

module instance named clocking, expecting identifier #1218

Closed
veripoolbot opened this issue Sep 20, 2017 · 3 comments
Closed

module instance named clocking, expecting identifier #1218

veripoolbot opened this issue Sep 20, 2017 · 3 comments
Labels
area: parser Issue involves SystemVerilog parsing resolution: no fix needed Closed; no fix required (not a bug)

Comments

@veripoolbot
Copy link
Contributor

Author Name: Edmond Cote (@edcote)
Original Redmine Issue: 1218 from https://www.veripool.org

I'm compiling some IP and the vendor chose to name the module instance as "clocking".

Here is the error :

Instantiated as you would expect.

ddr3_clks clocking (.reset               (rst_p),
                     .reset_datapath      (wl_rst_datapath),
                     .refclk              (clk_in), 
[..]
@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Edmond Cote (@edcote)
Original Date: 2017-09-20T23:11:25Z

Here's the test case:

module easyas123(); endmodule

module abc();
easyas123 clocking();
endmodule

Verilator 3.906 2017-06-22 rev verilator_3_904-11-g1da5a33

@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-09-21T00:35:45Z

Ask your vendor why they haven't fixed it in the 12 years since it became a IEEE keyword :)

Anyhow use "--language 1364-2001" or in the RTL use the IEEE standard begin_keywords "1364-2001" at the top, and at the bottom end_keywords

@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Edmond Cote (@edcote)
Original Date: 2017-09-21T17:56:13Z

Thanks for the reply, Wilson. I'll keep the above in mind.

@veripoolbot veripoolbot added area: parser Issue involves SystemVerilog parsing resolution: nofixneeded resolution: no fix needed Closed; no fix required (not a bug) and removed resolution: nofixneeded labels Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: parser Issue involves SystemVerilog parsing resolution: no fix needed Closed; no fix required (not a bug)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@veripoolbot