Bug of loopsUnroll for loops with one parser state #3492
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
What happens when you try this on #3142? |
mihaibudiu
approved these changes
Aug 25, 2022
parserUnroll still have a bugs for: spec-ex19.p4, gauntlet_parser_test_4.p4, issue2090.p4. I need to fix them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
loopsUnroll has a bug for unrolling loops with one parser state where such loop is restricted by header stack size only. These changes fix this bug. To see the problem, please, run:
./backends/p4test/p4test -I "p4include" --target bmv2 --std p4-16 --loopsUnroll --arch v1model ../testdata/p4_16_samples/stack_complex-bmv2.p4