[PATCH] D136383: [PartialInlining] Enable recursive partial inlining.

[Eli Friedman via Phabricator via llvm-commits]

efriedma added a comment.

The obvious concern for making inlining more aggressive is potential codesize growth.  Does the cost model prevent us from cloning the function multiple times?  How much growth are we talking about for practical code?



================
Comment at: llvm/test/Transforms/PartialInlining/recursive_partial_inlining.ll:1
+; NOTE: Assertions have been autogenerated by utils/update_test_checks.py
+; RUN: opt -partial-inliner -skip-partial-inlining-cost-analysis -S < %s | FileCheck %s
----------------
update_test_checks.py has a flag --include-generated-funcs you might want to use here.


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D136383