Searched refs:inliner (Results 1 – 23 of 23) sorted by relevance
| /external/proguard/src/proguard/preverify/ |
| D | SubroutineInliner.java | 57 ClassVisitor inliner = in execute() local
66 inliner = in execute()
68 inliner); in execute()
71 programClassPool.classesAccept(inliner); in execute()
|
| /external/llvm/test/Transforms/Inline/ |
| D | 2004-04-15-InlineDeletesCall.ll | 3 ; Inlining the first call caused the inliner function to delete the second
4 ; call. Then the inliner tries to inline the second call, which no longer
|
| D | inline-invoke-with-asm-call.ll | 4 ; In inliner, we assume that inline asm does not throw. This testing case makes
5 ; sure that the inliner does not convert "call asm" to "invoke asm".
|
| D | PR4909.ll | 1 ; RUN: opt < %s -partial-inliner -disable-output
|
| D | crash.ll | 3 ; This test was failing because the inliner would inline @list_DeleteElement
7 ; another one. This crashed the inliner because the new call was not in the
|
| D | inline_cleanup.ll | 1 ; Test that the inliner doesn't leave around dead allocas, and that it folds
63 ; No branches should survive the inliner's cleanup.
164 ; This previously crashed during inliner cleanup and folding inner return
|
| D | always-inline.ll | 19 ; The always inliner can't DCE internal functions. PR2945
30 ; The always inliner (unlike the normal one) should be willing to inline
|
| D | noinline-recursive-fn.ll | 1 ; The inliner should never inline recursive functions into other functions.
3 ; inliner heuristics are not set up for this.
|
| D | 2010-05-12-ValueMap.ll | 3 ; This tests for a bug where the inliner kept the functions in a ValueMap after
|
| D | lifetime.ll | 28 ;; Without this, the inliner will simplify out @test_no_marker before adding
|
| D | alloca-dbgdeclare-merge.ll | 1 ; Test that alloca merging in the inliner places dbg.declare calls immediately
|
| D | inline-fp.ll | 3 ; to the inliner.
|
| D | devirtualize.ll | 6 ; Simple devirt testcase, requires iteration between inliner and GVN.
|
| D | inline_invoke.ll | 3 ; Test that the inliner correctly handles inlining into invoke sites
|
| /external/llvm/test/Feature/OperandBundles/ |
| D | inliner-conservative.ll | 3 ; Check that the inliner does not inline through arbitrary unknown
|
| /external/llvm/test/Transforms/InstCombine/ |
| D | inline-intrinsic-assert.ll | 4 ; The inliner should not add an edge to an intrinsic and
|
| /external/llvm/test/Other/ |
| D | optimization-remarks-inline.ll | 7 ; second one we ask for the inliner, but we then ask for the vectorizer
|
| /external/v8/test/webkit/ |
| D | dfg-inline-constant-expected.txt | 24 …inlining in the DFG JIT doesn't get confused by constants being reused between inliner and inlinee.
|
| /external/llvm/docs/ |
| D | FAQ.rst | 414 code is perfectly well defined). If you run this through the inliner, you
415 get this (the explicit "or" is there so that the inliner doesn't dead code
437 with the wrong calling convention. We really don't want to make the inliner
440 if ``%X`` was an input argument to ``@test``, the inliner would produce this:
|
| D | Passes.rst | 386 A custom inliner that handles only functions that are marked as "always
919 ``-partial-inliner``: Partial Inliner
|
| D | ExceptionHandling.rst | 309 catches exceptions of type ``B``. The inliner will update the ``landingpad``
|
| D | LangRef.rst | 308 function definition. Furthermore the inliner doesn't consider such function
380 doesn't prevent the inliner from inlining the function call.
1137 the inliner and other passes to reason about the semantics of the function
1227 This attribute indicates that the inliner should attempt to inline
1258 inliner.
1295 This attribute indicates that the inliner should never inline this
1542 The inliner knows how to inline through calls that have deoptimization
1547 inliner does this by prepending the parent's deoptimization
|
| /external/clang/docs/ |
| D | UsersManual.rst | 538 done by compiler transformations. For instance, when the inliner
558 emit the associated diagnostic. For example, to get a report from the inliner,
568 Note that remarks from the inliner are identified with `[-Rpass=inline]`.
1155 frequently than another function ``bar`` helps the inliner.
|