[PATCH] D87865: PR47468: Fix findPHICopyInsertPoint, so that copies aren't incorrectly inserted after an INLINEASM_BR.

Bill Wendling via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Thu Sep 17 16:36:01 PDT 2020


void added inline comments.


================
Comment at: llvm/lib/CodeGen/PHIEliminationUtils.cpp:57
+    if ((EHPadSuccessor && I->isCall()) ||
+        I->getOpcode() == TargetOpcode::INLINEASM_BR) {
+      InsertPoint = I.getReverse();
----------------
efriedma wrote:
> Is it possible to have multiple INLINEASM_BR instructions in the same block?  If it is, we need to find the first one, not the last one.
It shouldn't come to that. The `callbr` is a terminator, and an MBB with an INLINEASM_BR will have multiple successors, so there shouldn't be block merging.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D87865/new/

https://reviews.llvm.org/D87865



More information about the llvm-commits mailing list