Skip to content
This repository was archived by the owner on Jun 26, 2020. It is now read-only.
This repository was archived by the owner on Jun 26, 2020. It is now read-only.

Dominator tree #2

@stoklund

Description

@stoklund

Cretonne's in-memory IR needs a dominator tree analysis for verification, and likely for register allocation.

We expect most input programs to have structured control flow, so the Cooper / Harvey / Kennedy algorithm will work well.

  • Should the dominator tree be a static analysis, or should it be dynamically updated when the CFG (Control flow graph #1) changes?
  • How does a dominator tree interact with EBBs? The immediate dominator of every inner basic block in an EBB is obvious (it's the previous basic block), so it doesn't need to be stored. Inly the immediate dominator of an EBB is interesting.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions