Chris Dodd

For #1144

Standard annotations for expected code path to optimize

12

There should be a way for the programmer to indicate which path through a control or parser should be the most common and should be optimized for. One possibility would...

Arrays of non-header types

2

P4 uses array syntax for header stacks, which are declared like arrays of a header type and can be indexed with normal (C/java) array indexing syntax, but also support some...

Support for op= assignments in the frontend/midend

14

- these are parsed as IR::OpAssignmentStatements - they are (optionally) converted to normal assignments in the frontend - they may be kept as special nodes by backends that desire to...

Pass to get rid of action_run() calls

11

This is a general midend pass for any target that does not support `action_run` directly. It rewrites the actions in a table that uses action_run to set a newly introduced...

In trying to use the JSONGenerator/Loader code for additional things, I found a number of ways in which they are tricky to use and easy to use incorrectly (as well...

Add @likely/@unlikely annotations for blocks

6

These will generally be used by backends and simply passed through the frontend/midend, so not much is needed here. Perhaps some frontend passes (in particular, DoSimplifyControlFlow in frontends/p4/simplify.cpp) could be...