-
Notifications
You must be signed in to change notification settings - Fork 444
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
Enhancement: program that accepts all legal P4_16 programs #530
Labels
enhancement
This topic discusses an improvement to existing compiler code.
fixed
This topic is considered to be fixed.
Comments
The only thing needed is to stop compilation after the front-end is finished. |
Sorry for my ignorance in asking, but is there already a p4test command line option (or collection of options) that achieves this, and if so, what is it? |
No. But that would be the fix. |
mihaibudiu
added
the
enhancement
This topic discusses an improvement to existing compiler code.
label
Apr 27, 2017
mihaibudiu
pushed a commit
to mihaibudiu/p4c-clone
that referenced
this issue
Nov 9, 2017
Tested with new --validate option on the same program on issue #513 that causes p4test to issue an error, and it gives no error. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
This topic discusses an improvement to existing compiler code.
fixed
This topic is considered to be fixed.
p4test is pretty close to this already, but for various reasons it does not accept some syntactically and semantically legal P4_16 programs as of 2017-Apr-26, e.g. see #513
Given how close p4test is to this, one possible implementation might be to add a new p4test command line option that changes its behavior somewhat, enabling it to accept all legal P4_16 programs, e.g. --validate
The text was updated successfully, but these errors were encountered: