[FTD] Simplifying FTD to One Suppression per Data Delivery #620
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.
Motivation
The previous FTD implementation handled loops by splitting them into four distinct scenarios.
When a single data delivery simultaneously matched multiple scenarios, or when deliveries appeared inside nested loops, the pass inserted multiple
cond_brto realize suppression.This increased circuit area and control complexity, making behavior hard to reason about.
This PR focuses purely on simplification: each data delivery is guarded by exactly one suppression branch.
We adopt a unified handling that does not require classifying loop scenarios into four cases and does not stack multiple branches for overlapping situations.
Implementation
If the producer is traversed again, it is treated as the sink.
All such cases are managed through one unified suppression path.
cond_brat the delivery site.