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

error type in core.p4 not saved in parser symbol table? #437

Closed
hanw opened this issue Apr 5, 2017 · 0 comments
Closed

error type in core.p4 not saved in parser symbol table? #437

hanw opened this issue Apr 5, 2017 · 0 comments

Comments

@hanw
Copy link
Contributor

hanw commented Apr 5, 2017

Is the P4 error type saved in symbol table during parsing?

error { NoError , ... }

I am getting a few error messages when I try to run add a second unit test to the same gtest file.

(null)(5): error: NoError: Duplicates declaration NoError
 error {     NoError,     PacketTooShort,     NoMatch,     StackOutOfBounds,     OverwritingHeader,     HeaderTooShort,     ParserTimeout }
             ^^^^^^^
(null)(5): error: PacketTooShort: Duplicates declaration PacketTooShort
 error {     NoError,     PacketTooShort,     NoMatch,     StackOutOfBounds,     OverwritingHeader,     HeaderTooShort,     ParserTimeout }
                          ^^^^^^^^^^^^^^
...

The problem is not because of existing entries in symbol table, which are already cleared with a clear function to remove all entries in symbol table after each run.

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

1 participant