MoveInitializers
splits start
state for parsers that do not need this
#4901
Labels
core
Topics concerning the core segments of the compiler (frontend, midend, parser)
If
MoveInitializers
detects that a parser needs astart
state split,start
also gets split for all the other parsers that follow that first parser in the P4 IR, even if they do not need this.Parser2
in the code below does not needstart
split:However, the frontend's output is:
The midend is able to squash
start_0
andstart
forParser2
above, but there is still no reason to split.The text was updated successfully, but these errors were encountered: