-
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
Add a p4-constraints and @refers_to parser to P4Tools. #3568
Conversation
[no-jira]
[no-jira]
…into Restrictions [no-jira]
[no-jira]
[no-jira]
[no-jira]
I will run this code tomorrow to see whether it is complete. Can you refresh it? |
I tried to clean up some of the code but there is lots of work left. This code has a lot of problems. I attached a patch, please apply it. |
[no-jira]
[no-jira]
[no-jira]
[no-jira]
[no-jira]
I went through the code again, there are still items left to do. I made some comments. Here is a new patch that should be applied. |
Another patch. |
Another patch set to apply. |
Can you update this to the latest changes in master? We should run the gtests to check before merging. |
This is the implementation of p4-constraints for P4Tools , it allows you to convert the expression in string format from the body of the
@entry_restriction
or@refers_to
annotation into an IR expression and compose the restrictions for the tool from them.These restrictions are added as preconditions to the P4Tools BMv2 execution.