Don't apply loop condition to pipelined loops when it is proven true for the first iteration. #2534
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.
Don't apply loop condition to pipelined loops when it is proven true for the first iteration.
Also add several continuation optimizations to yield a clean data flow graph
for nested pipelined loops.
NOTE: Logic enabling narrowing was temporarily removed from generate_fsm.cc.
This is because when the loop body is unguarded by the loop condition,
as when the first iteration is proven to always have a true condition,
nested loops are broken by this logic. This is because the state element
isn't updated after the last iteration / activation of the (inner) loop, since
the condition being used for this is the jump condition of the loop.
The next_value() generation logic will soon be reworked, so for now this has been
temporarily removed.