[PATCH] D54730: [DomTree] Fix order of domtree updates in MergeBlockIntoPredecessor.

[Jakub Kuderski via Phabricator via llvm-commits]

kuhar added a comment.

We experimented with different ordering of updates before, including scheduling deletions before insertions, but didn't discover any promising strategies. Because of that, updates are performed in the exact order they were scheduled (except optimizing out trivially redundant ones).

The preferred API to use is currently DomTreeUpeater, but I don't think it would affect performance here.

Any thoughts @NutshellySima?


Repository:
  rL LLVM

https://reviews.llvm.org/D54730