| /external/jsilver/src/com/google/clearsilver/jsilver/interpreter/ |
| D | OptimizingTemplateFactory.java | 44 for (OptimizerProvider optimizer : optimizers) { in OptimizingTemplateFactory()
45 if (optimizer != null) { in OptimizingTemplateFactory()
46 this.optimizers.add(optimizer); in OptimizingTemplateFactory()
52 for (OptimizerProvider optimizer : optimizers) { in optimize()
53 ast.apply(optimizer.getOptimizer()); in optimize()
|
| /external/llvm/docs/ |
| D | LinkTimeOptimization.rst | 14 interface and design between the LTO optimizer and the linker.
26 bitcode files. This tight integration between the linker and LLVM optimizer
28 input allows the optimizer to avoid relying on conservative escape analysis.
97 anywhere. This information is used by the LLVM optimizer and it
100 * As soon as ``foo2()`` is removed, the optimizer recognizes that condition ``i
102 optimizer also removes ``foo3()``.
107 linker. Here, the optimizer can not remove ``foo3()`` without the linker's
113 **Compiler driver invokes link time optimizer separately.**
114 In this model the link time optimizer is not able to take advantage of
116 In the above example, the optimizer can not remove ``foo2()`` without the
[all …]
|
| D | HowToSubmitABug.rst | 42 the LLVM libraries (e.g. the optimizer or code generator) that has
45 To figure out which component is crashing (the front-end, optimizer or code
50 options (which disable the optimizer and code generator), then the crash
55 the code generator), you found an optimizer bug. Jump ahead to
86 If you find that a bug crashes in the optimizer, compile your test-case to a
|
| D | ExtendedIntegerResults.txt | 79 might want the callee to extend 3) the mid-level optimizer doesn't know the
114 The one thing that is missing is the ability for the front-end and optimizer to
121 and given that it is stuck on the y function, the mid-level optimizer could
|
| /external/chromium_org/third_party/jinja2/ |
| D | optimizer.py | 26 optimizer = Optimizer(environment)
27 return optimizer.visit(node)
|
| /external/chromium_org/third_party/WebKit/Source/core/rendering/ |
| D | RenderImage.cpp | 576 void RenderImage::didLayout(ResourceLoadPriorityOptimizer& optimizer) in didLayout() argument
578 RenderReplaced::didLayout(optimizer); in didLayout()
579 updateImageLoadingPriority(optimizer); in didLayout()
582 void RenderImage::didScroll(ResourceLoadPriorityOptimizer& optimizer) in didScroll() argument
584 RenderReplaced::didScroll(optimizer); in didScroll()
585 updateImageLoadingPriority(optimizer); in didScroll()
588 void RenderImage::updateImageLoadingPriority(ResourceLoadPriorityOptimizer& optimizer) in updateImageLoadingPriority() argument
607 optimizer.notifyImageResourceVisibility(m_imageResource->cachedImage(), status); in updateImageLoadingPriority()
|
| /external/chromium_org/third_party/WebKit/Source/build/scripts/ |
| D | make_token_matcher_unittest.py | 38 optimizer = Optimizer(None, None, None)
41 optimizer.inspect_array,
|
| /external/chromium_org/third_party/sqlite/src/test/ |
| D | tkt3757.test | 12 # Ticket #3757: The cost functions on the query optimizer for the
42 # Modify statistics in order to make the optimizer then that:
|
| D | tkt-26ff0c2d1e.test | 12 # focus of this script testing a bug found in the OP_Variable optimizer
|
| D | tkt2640.test | 17 # The problem in ticket #2640 was that the query optimizer was
24 # optimizer would not recognize this and would try to evaluate
|
| D | tkt2643.test | 17 # The problem in ticket #2643 has to do with the query optimizer
|
| /external/proguard/bin/ |
| D | proguard.bat | 3 REM Start-up script for ProGuard -- free class file shrinker, optimizer,
|
| D | proguardgui.bat | 4 REM optimizer, obfuscator, and preverifier for Java bytecode.
|
| D | retrace.bat | 4 REM shrinker, optimizer, obfuscator, and preverifier for Java bytecode.
|
| /external/llvm/test/Transforms/InstCombine/ |
| D | 2006-10-19-SignedToUnsignedCastAndConst-2.ll | 1 ; The optimizer should be able to remove cast operation here.
|
| D | 2003-07-21-ExternalConstant.ll | 10 ; should pass through the optimizer without failure.
|
| /external/clang/test/CodeGenObjC/ |
| D | exceptions.m | 110 // This loop is large enough to dissuade the optimizer from just
115 // on a specific result from the optimizer is really unstable.
120 // on a specific result from the optimizer is really unstable.
|
| /external/llvm/test/CodeGen/R600/ |
| D | fcmp-cnd.ll | 4 ;registers and literal.x depending on what the optimizer does.
|
| /external/chromium_org/third_party/sqlite/ |
| D | fts3_85522.patch | 4 fts3.c uses 'PRAGMA page_size' to tune the query optimizer, but PRAGMA
|
| /external/llvm/test/Transforms/SCCP/ |
| D | calltest.ll | 4 ; optimizer to delete this loop.
|
| /external/llvm/test/CodeGen/PowerPC/ |
| D | coalesce-ext.ll | 2 ; Check that the peephole optimizer knows about sext and zext instructions.
|
| /external/llvm/test/CodeGen/X86/ |
| D | and-or-fold.ll | 17 ; <rdar://problem/7529774> The optimizer shouldn't fold this into (and (or, C), D)
|
| /external/proguard/ |
| D | README | 1 ProGuard, Java class file shrinker, optimizer, obfuscator, and preverifier
|
| /external/llvm/examples/OCaml-Kaleidoscope/Chapter6/ |
| D | toy.ml | 28 (* Set up the optimizer pipeline. Start with registering info about how the
|
| /external/llvm/examples/OCaml-Kaleidoscope/Chapter4/ |
| D | toy.ml | 28 (* Set up the optimizer pipeline. Start with registering info about how the
|