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

Parser reports incorrect filename / linenumber when parsing SystemVerilog class #1162

Closed
veripoolbot opened this issue May 16, 2017 · 2 comments
Closed

Parser reports incorrect filename / linenumber when parsing SystemVerilog class #1162

veripoolbot opened this issue May 16, 2017 · 2 comments
Assignees
@wsnyder

Comments

@veripoolbot
Copy link
Collaborator

Author Name: Dave Storrar
Original Redmine Issue: 1162 from https://www.veripool.org

Original Assignee: Wilson Snyder (@wsnyder)

I'm using a basic subclass of SigParser which reports when certain items are defined I noticed that the "filename" and "lineno" methods can report incorrect information when a class is encountered.

Attached testcase shows the problem.
The SystemVerilog file contains three classes:

  1. I2CTiming which reports the correct line-number but wrong file (Perl_Verilog::Std_module).
  2. I2CTiming2 which is a virtual class (and reports correctly).
  3. I2CTiming3 which reports the same information as I2CTiming2.

(Note: I'm still on version 3.418, but I don't think anything related to this has changed since).
@veripoolbot
Copy link
Collaborator Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-05-17T01:39:07Z

Thanks for the example.

Fixed in git towards 3.435. I'll hold releasing this a bit in case you find more problems.

@veripoolbot
Copy link
Collaborator Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-09-09T01:56:42Z

In 3.442.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wsnyder wsnyder

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wsnyder @veripoolbot