Merge basic blocks #561
Assignees
Comments
|
@acl-cqc We discussed this morning where this sort of thing (also #818 ) should go, and the general agreement that there should be a "hugr-passes" crate, in the hugr repo, where passes that operate on general HUGRs go. (Other quantum-specific passes would go in the TKET2 repo.) This makes for a cleaner separation between passes (which shouldn't rely on hugr internals) and core hugr. Does this seem reasonable? |
This was referenced May 1, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
May 10, 2024
Any basic block with a single successor that has no other predecessors can be merged. (So long as the successor is not the exit block; nor the entry block, as that implicitly has another predecessor). Implement via Replace (2 BBs - > one BB containing 2 DFGs, which adopt the original BB's children) and 2*InlineDFG. Closes #561.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i.e. when there is an edge from a BB with only one successor, to a BB with only one predecessor, the two can be combined. As a first step this would produce one BB containing two DFG nodes one of which consumes all outputs of the other, but then 2*InlineDFG operations to flatten them should remove false dependencies and enable additional optimizations.
Might require implementing both Replacement and/or InlineDFG rewrites...
The text was updated successfully, but these errors were encountered: