You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The P4 language design working group has stated that P4 is an unsafe language. So what I suggested as a better alternative in the wiki entry above will likely not be realized in the foreseeable future. However, we can try to detect these sorts of uses as much as possible at compile time.
The text was updated successfully, but these errors were encountered:
This currently causes a crash in x4c compiled code. A good question is
what should happen here. According to P4 spec x4c should emit an
unspecified value. According to ry we should apport the pipeline.
- #6
Perhaps we can catch some of these at compile time?
- #7
For context see this wiki entry.
https://github.com/oxidecomputer/p4/wiki/P4-Specification-Notes#reading-uninitialized-values
The P4 language design working group has stated that P4 is an unsafe language. So what I suggested as a better alternative in the wiki entry above will likely not be realized in the foreseeable future. However, we can try to detect these sorts of uses as much as possible at compile time.
The text was updated successfully, but these errors were encountered: