-
Notifications
You must be signed in to change notification settings - Fork 92
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
P4 @name
annotations contain perhaps-unsupported characters
#347
Comments
Hi Andy, @marian-pritsak would have more to say on this, but so far I am not aware of any problems resulting from the current DASH annotations. Also be aware that there is/was work underway to address #276 by adding custom annotations to direct the SAI code generator and remove the |
Thanks for opening this issue @jafingerhut. Yes, this issue is largely internal and will only become a problem when the IR is serialized into |
ok, with the latest updates in DASH, all usage of "|" or ":" in the name are removed. we should not have this issue anymore. @jafingerhut and @fruffy do you have any other concerns on the name? |
Yes, we also fixed this problem with a couple compiler fixes for the inlining pass. Thanks for keeping track of this! |
Np at all! I guess we can finally get this long running issue closed! 🎉 |
Closing per thread |
It is not clear to me yet, but perhaps open source p4c and/or its P4Runtime API implementation might not support characters in
@name
annotations that are not legal P4 identifiers. For example, it might not support the|
character in this annotation:DASH/dash-pipeline/bmv2/dash_pipeline.p4
Line 201 in 611a15f
See this p4c issue where @fruffy has been facing difficulties in this area: p4lang/p4c#3885
The text was updated successfully, but these errors were encountered: