[build] Switch BMv2 p4 compiler from p4c to p4c-bm2-ss. #494
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
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.
p4c-bm2-ss is a dedicated compiler built for building bmv2 code. Unlike p4c-ss and p4c-bm, this compiler is using the latest code, directly built from the p4c backend.
Switching to this compiler will not change the generated content, but it will give us more access on more command line options instead of being limited to the small set of the parameters provided by p4c, e.g. dumping IRs, which may give us more information for generating SAI in a more smarter way.
Similarly, we are already doing it for DPDK - using p4c-dpdk instead of p4c -b dpdk.