[PATCH] D87262: [Inliner] Apply llvm.loop.mustprogress to caller loops
Atmn Patel via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Mon Sep 7 18:53:48 PDT 2020
atmnpatel created this revision.
atmnpatel added reviewers: jdoerfert, hfinkel.
Herald added subscribers: llvm-commits, hiraditya, eraman.
Herald added a project: LLVM.
atmnpatel requested review of this revision.
When inlining `maynotprogress` functions, the caller will also need to
inherit the `maynotprogress` attribute (D87180 <https://reviews.llvm.org/D87180>) for correctness, if it
doesn't already have it. In addition, the loops in the caller must also
be annotated with `llvm.loop.mustprogress` in order to not pessimize
optimizations. This only works from within the new pass manager.
Repository:
rG LLVM Github Monorepo
https://reviews.llvm.org/D87262
Files:
llvm/include/llvm/Analysis/LoopInfo.h
llvm/include/llvm/Transforms/Utils/Cloning.h
llvm/lib/Analysis/LoopInfo.cpp
llvm/lib/Transforms/IPO/Inliner.cpp
llvm/lib/Transforms/Utils/InlineFunction.cpp
llvm/test/Transforms/Inline/inlined-mustprogress-loop-metadata.ll
llvm/test/Transforms/Inline/maynotprogress.ll
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D87262.290390.patch
Type: text/x-patch
Size: 8184 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20200908/a3f22303/attachment.bin>
More information about the llvm-commits
mailing list