/external/clang/docs/analyzer/ |
D | IPA.txt | 5 inlining. The major one is -analyzer-config ipa: 7 -analyzer-config ipa=none - All inlining is disabled. This is the only mode 10 -analyzer-config ipa=basic-inlining - Turns on inlining for C functions, C++ 15 -analyzer-config ipa=inlining - Turns on inlining when we can confidently find 39 ### c++-inlining ### 43 -analyzer-config c++-inlining=[none | methods | constructors | destructors] 46 inlined as well; it doesn't make sense to inline destructors without inlining 49 The default c++-inlining mode is 'destructors', meaning that all member 50 functions with visible definitions will be considered for inlining. In some 55 inlined under -analyzer-config ipa=none or -analyzer-config ipa=basic-inlining, [all …]
|
D | nullability.rst | 63 …ed body. For example, consider these conversions from nonnull to nullable in presence of inlining:: 73 …inlining is not robust enough (for example there might be more parameters with different nullabili…
|
/external/proguard/src/proguard/optimize/peephole/ |
D | MethodInliner.java | 77 private boolean inlining; field in MethodInliner 152 if (inlining) in visitCodeAttribute() 165 if (inlining) in visitCodeAttribute() 178 if (!inlining) in visitCodeAttribute0() 366 if (inlining) in visitSimpleInstruction() 406 if (inlining) in visitVariableInstruction() 436 !inlining && in visitConstantInstruction() 462 if (inlining) in visitConstantInstruction() 562 boolean oldInlining = inlining; in visitProgramMethod() 563 inlining = true; in visitProgramMethod() [all …]
|
/external/llvm/docs/CommandGuide/ |
D | llvm-symbolizer.rst | 61 $llvm-symbolizer -inlining -print-address -pretty-print -obj=addr.exe < addr.txt 64 $llvm-symbolizer -inlining -pretty-print -obj=addr.exe < addr.txt 90 .. option:: -inlining 115 Print human readable output. If ``-inlining`` is specified, enclosing scope is
|
/external/llvm/test/Transforms/Inline/ |
D | ephemeral.ll | 10 ; Here are enough instructions to prevent inlining, but because they are used 11 ; only by the @llvm.assume intrinsic, they're free (and, thus, inlining will
|
D | dynamic_alloca_test.ll | 2 ; naively inlining it would result in a miscompilation. 9 ; inlining of functions which contain a dynamic alloca. It should be re-enabled
|
D | cfg_preserve_test.ll | 1 ; This test ensures that inlining an "empty" function does not destroy the CFG
|
D | inline-indirect.ll | 3 ; inlining the indirect call
|
D | inline-tail.ll | 6 ; No tail marker after inlining, since test_capture_c captures an alloca. 22 ; No musttail marker after inlining, since the prototypes don't match. 37 ; After inlining through a musttail call site, we need to keep musttail markers
|
D | inline-assume.ll | 6 ; Test that we don't crash when inlining @bar (rdar://22521387).
|
D | inline-musttail-varargs.ll | 21 ; FIXME: Inline the thunk. This should be significantly easier than inlining
|
D | byval_lifetime.ll | 4 ; By inlining foo, an alloca is created in main to hold the byval argument, so
|
D | invoke-cleanup.ll | 20 ; Test that the "cleanup" clause is kept when inlining @inner() into
|
D | inline-fast-math-flags.ll | 2 ; Check that we don't drop FastMathFlag when estimating inlining profitability.
|
/external/llvm/test/DebugInfo/ |
D | llvm-symbolizer.test | 25 RUN: echo "%p/Inputs/cross-cu-inlining.x86_64-macho.o 0x17" >> %t.input 27 RUN: llvm-symbolizer --functions=linkage --inlining --demangle=false \ 116 CHECK-NEXT: /tmp{{[/\\]}}cross-cu-inlining.c:16:3 118 CHECK-NEXT: /tmp{{[/\\]}}cross-cu-inlining.c:11:0
|
/external/llvm/test/DebugInfo/Generic/ |
D | debug-info-always-inline.ll | 28 ; are attributed with the call site's DebugLoc. After inlining, inlined static 52 ; At some point in the future, it may be desirable to describe the inlining 61 ; have their DebugLocs augmented with inlining information. 64 ; Make sure that after inlining the call to foo() the alloca instructions for
|
/external/clang/test/Analysis/ |
D | objc-method-coverage.m | 16 // CHECK: 2 AnalysisConsumer - The # of functions and blocks analyzed (as top level with inlining t…
|
D | default-analyze.m | 22 // Note: this requires inlining support. This previously issued a false positive use of
|
/external/llvm/test/tools/llvm-symbolizer/ |
D | coff-dwarf.test | 2 RUN: | llvm-symbolizer --inlining --relative-address -obj="%p/Inputs/coff-dwarf.exe" \
|
D | coff-exports.test | 2 RUN: | llvm-symbolizer --inlining --relative-address -obj="%p/Inputs/coff-exports.exe" \
|
D | sym.test | 21 RUN: llvm-symbolizer -inlining -print-address -pretty-print -obj=%p/Inputs/addr.exe < %p/Inputs/add…
|
/external/clang/test/Analysis/inlining/ |
D | test_objc_inlining_option.m | 1 …checker=core -analyzer-config ipa=dynamic-bifurcate -analyzer-config objc-inlining=false -verify %s
|
/external/v8/src/third_party/fdlibm/ |
D | README.v8 | 16 tangent. To make inlining into generated code possible, a large portion of
|
/external/llvm/test/CodeGen/PowerPC/ |
D | fsl-e5500.ll | 2 ; Test support for Freescale e5500 and its higher memcpy inlining thresholds.
|
D | fsl-e500mc.ll | 2 ; Test support for Freescale e500mc and its higher memcpy inlining thresholds.
|