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

Incorrectly parse the error/warning information of iverilog when linting. #166

Open
simon-zh-1234 opened this issue Jul 26, 2021 · 0 comments
Labels

Comments

@simon-zh-1234
Copy link

Describe the bug
The extension cannot parse the output information of iverilog correctly, say, it does not know how to determine the location of colon.
For example, I have two files float_add.v and test.v, in the former one two module float_add and test are defined and in the later one test are defined again by mistake. And in test.v I include float_add.v.
If I run iverilog test.v -t null, the output is
test.v:46: Module test was already declared here: ./float_add.v:69
However, if I save test.v in editor, the linting information is only
./float_add.v
Obviously here colon is incorrectly parsed.

Environment:

  • OS: Ubuntu 20.04 with Linux 5.8.0-63-generic.
  • VS Code version [1.58.2]
  • Extension version [1.5.0]
  • lint tool is iverilog

Steps to reproduce
Steps to reproduce the behavior:

  1. Create two file float_add.v and test.v
  2. write two module float_add and test in float_add.v
  3. include float_add.v in test.v and write a module test in test.v
  4. Save float_add.v and test.v, compare the linting information in test.v and the output of iverilog test.v -t null
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant