Home
last modified time | relevance | path

Searched refs:aggressively (Results 1 – 25 of 25) sorted by relevance

/external/llvm/test/CodeGen/X86/
Dtwoaddr-coalesce-2.ll3 ; RUN: grep "twoaddrinstr" | grep "Number of instructions aggressively commuted"
/external/chromium_org/chrome/browser/history/
Dhistory_database.h135 void TrimMemory(bool aggressively);
Dhistory_database.cc232 void HistoryDatabase::TrimMemory(bool aggressively) { in TrimMemory() argument
233 db_.TrimMemory(aggressively); in TrimMemory()
Dthumbnail_database.h62 void TrimMemory(bool aggressively);
Dthumbnail_database.cc641 void ThumbnailDatabase::TrimMemory(bool aggressively) { in TrimMemory() argument
642 db_.TrimMemory(aggressively); in TrimMemory()
/external/chromium_org/components/precache/core/proto/
Dprecache.proto31 // testing purposes, so that it's easy to adjust how aggressively resources
/external/llvm/test/Transforms/IndVarSimplify/
D2014-06-21-congruent-constant.ll6 ; folded away aggressively if spelled out in IR directly.
/external/chromium_org/sql/
Dconnection.h207 void TrimMemory(bool aggressively);
Dconnection.cc350 void Connection::TrimMemory(bool aggressively) { in TrimMemory() argument
364 int shrink_cache_size = aggressively ? 1 : (original_cache_size / 2); in TrimMemory()
/external/chromium_org/v8/test/webkit/
Ddfg-captured-var-get-local-expected.txt24 Tests that GetLocals on captured variables aren't eliminated too aggressively.
/external/llvm/docs/HistoricalNotes/
D2003-06-26-Reoptimizer2.txt37 It is not aggressively able to use lots of registers.
/external/llvm/lib/CodeGen/
DREADME.txt63 LLVM aggressively lift CSE out of loop. Sometimes this can be negative side-
/external/eigen/doc/
DTopicAliasing.dox113 are doing. This may also allow %Eigen to optimize more aggressively. These are some of the xxxInPla…
/external/proguard/src/proguard/gui/
DGUIResources.properties97 mergeInterfacesAggressively = Merge interfaces aggressively
107 overloadAggressively = Overload aggressively
/external/chromium_org/native_client_sdk/src/doc/sdk/
Dexamples.rst156 Chrome's intelligent caching caches resources aggressively. When building a
/external/chromium_org/native_client_sdk/src/doc/devguide/tutorial/
Dtutorial-part1.rst104 Chrome cache. Chrome caches resources aggressively; disabling the cache helps
/external/llvm/include/llvm/IR/
DIntrinsics.td368 // optimizers can change them aggressively. Special handling needed in a few
/external/libunwind/doc/
Dlibunwind.tex278 To speed up execution, \Prog{libunwind} may aggressively cache the
/external/chromium_org/native_client_sdk/src/doc/devguide/devcycle/
Drunning.rst158 Chrome caches resources aggressively. You should disable Chrome's cache whenever
/external/clang/docs/analyzer/
DIPA.txt32 While -analyzer-config ipa determines in general how aggressively the analyzer
/external/llvm/lib/Target/
DREADME.txt607 matching code in dag combine doesn't look through truncates aggressively
1583 functionattrs doesn't handle memset/memcpy/memmove aggressively:
1958 aggressively as malloc though.
/external/llvm/lib/Target/X86/
DX86InstrArithmetic.td1019 /// tblgen can't handle dependent type references aggressively enough: PR8330
1090 /// tblgen can't handle dependent type references aggressively enough: PR8330
DREADME.txt1086 more aggressively; it should cost the same as a move+shift on any modern
/external/llvm/docs/
DPasses.rst378 ADCE aggressively tries to eliminate code. This pass is similar to :ref:`DCE
/external/e2fsprogs/
DRELEASE-NOTES2676 aggressively as an optimization to avoid copying the array too often.