[PATCH] D76248: Fix a bug in the legacy inliner that causes subseqeunt double inlining.

Wenlei He via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Thu Mar 19 12:35:33 PDT 2020


wenlei accepted this revision.
wenlei added a comment.
This revision is now accepted and ready to land.

In D76248#1931542 <https://reviews.llvm.org/D76248#1931542>, @hoyFB wrote:

> In D76248#1931511 <https://reviews.llvm.org/D76248#1931511>, @wenlei wrote:
>
> > Thanks for fixing this! I forgot to ask earlier, but this could happen with inlining under new PM as well, right? With new PM, we collect calls within SCC, then iterate over them for inlining, so for the same reason we could have dangling call in `VMap` from cloning?
>
>
> Yes, it could, though that didn't happen in our case. I think it's due to different orders calls are processed in the legacy and new inliner.


Ok, then change the title/description to reflect that (not legacy PM specific)? otherwise LGTM.


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D76248





More information about the llvm-commits mailing list