llvm-project.git/mlir/test/lib/Transforms/TestInliningCallback.cpp, branch main Unnamed repository; edit this file 'description' to name the repository. [mlir][NFC] update `mlir/Dialect` create APIs (28/n) (#150641) 2025-07-25T16:48:00+00:00 Maksim Levental maksim.levental@gmail.com 2025-07-25T16:48:00+00:00 258d04c810ab10f101324cbf1fe3c7be65eb1938 See https://github.com/llvm/llvm-project/pull/147168 for more info. 
See https://github.com/llvm/llvm-project/pull/147168 for more info.
 [mlir][inliner] Move callback types from InlinerConfig -> InlinerInterface. NFC. 2025-04-06T11:02:42+00:00 Benjamin Kramer kramerb@google.com 2025-04-06T11:00:14+00:00 3e08dcd767a217fa91580704a378b37167e20f74 The proper layering here is that Inliner depends on InlinerUtils, and not the other way round. Maybe it's time to give InliningUtils a less terrible file name. 
The proper layering here is that Inliner depends on InlinerUtils, and
not the other way round. Maybe it's time to give InliningUtils a less
terrible file name.
[mlir][inliner] Add doClone and canHandleMultipleBlocks callbacks to Inliner Config (#131226) 2025-04-05T20:56:55+00:00 junfengd-nv junfengd@nvidia.com 2025-04-05T20:56:55+00:00 aeec94500a5dbd576e5d2d16895fe00fa0b1e154 Current inliner disables inlining when the caller is in a region with single block trait, while the callee function contains multiple blocks. the SingleBlock trait is used in operations such as do/while loop, for example fir.do_loop, fir.iterate_while and fir.if. Typically, calls within loops are good candidates for inlining. However, functions with multiple blocks are also common. for example, any function with "if () then return" will result in multiple blocks in MLIR. This change gives the flexibility of a customized inliner to handle such cases. doClone: clones instructions and other information from the callee function into the caller function. . canHandleMultipleBlocks: checks if functions with multiple blocks can be inlined into a region with the SingleBlock trait. The default behavior of the inliner remains unchanged. --------- Co-authored-by: jeanPerier <jean.perier.polytechnique@gmail.com> Co-authored-by: Mehdi Amini <joker.eph@gmail.com> 
Current inliner disables inlining when the caller is in a region with
single block trait, while the callee function contains multiple blocks.
the SingleBlock trait is used in operations such as do/while loop, for
example fir.do_loop, fir.iterate_while and fir.if. Typically, calls within
loops are good candidates for inlining. However, functions with multiple
blocks are also common. for example, any function with "if () then
return" will result in multiple blocks in MLIR.

This change gives the flexibility of a customized inliner to handle such
cases.
doClone: clones instructions and other information from the callee
function into the caller function. .
canHandleMultipleBlocks: checks if functions with multiple blocks can be
inlined into a region with the SingleBlock trait.

The default behavior of the inliner remains unchanged.

---------

Co-authored-by: jeanPerier <jean.perier.polytechnique@gmail.com>
Co-authored-by: Mehdi Amini <joker.eph@gmail.com>