Searched refs:aggressive (Results 1 – 25 of 55) sorted by relevance
123
/external/ipsec-tools/src/racoon/samples/ |
D | racoon.conf.sample-inherit | 11 exchange_mode main,aggressive; 32 exchange_mode aggressive;
|
D | racoon.conf.in | 55 exchange_mode main,aggressive; 76 #exchange_mode main,aggressive; 77 exchange_mode aggressive,main;
|
D | racoon.conf.sample | 23 #exchange_mode main,aggressive,base;
|
D | racoon.conf.sample-natt | 62 exchange_mode main,base,aggressive;
|
/external/ipsec-tools/src/racoon/samples/roadwarrior/client/ |
D | racoon.conf | 9 exchange_mode aggressive;
|
/external/ipsec-tools/src/racoon/samples/roadwarrior/server/ |
D | racoon.conf | 8 exchange_mode aggressive;
|
D | racoon.conf-radius | 8 exchange_mode aggressive;
|
/external/llvm/test/CodeGen/ARM/ |
D | 2011-04-11-MachineLICMBug.ll | 3 ; Overly aggressive LICM simply adds copies of constants
|
/external/clang/test/SemaObjC/ |
D | warn-unreachable.m | 1 // RUN: %clang %s -fsyntax-only -Xclang -verify -fblocks -Wunreachable-code-aggressive -Wno-unused-…
|
/external/llvm/test/Transforms/TailCallElim/ |
D | accum_recursion.ll | 21 ; This is a more aggressive form of accumulator recursion insertion, which
|
/external/libmtp/ |
D | configure.ac | 95 # Stick in "-Werror" if you want to be more aggressive.
|
/external/yaffs2/yaffs2/ |
D | yaffs_guts.c | 2022 int aggressive) in yaffs_FindBlockForGarbageCollection() argument 2049 aggressive = 1; /* Fool the non-aggressive skip logiv below */ in yaffs_FindBlockForGarbageCollection() 2065 if (!aggressive && (nonAggressiveSkip > 0)) { in yaffs_FindBlockForGarbageCollection() 2071 (aggressive) ? dev->nChunksPerBlock : YAFFS_PASSIVE_GC_CHUNKS + 1; in yaffs_FindBlockForGarbageCollection() 2073 if (aggressive) { in yaffs_FindBlockForGarbageCollection() 2537 int aggressive; in yaffs_CheckGarbageCollection() local 2561 aggressive = 1; in yaffs_CheckGarbageCollection() 2564 aggressive = 0; in yaffs_CheckGarbageCollection() 2567 block = yaffs_FindBlockForGarbageCollection(dev, aggressive); in yaffs_CheckGarbageCollection() 2571 if (!aggressive) { in yaffs_CheckGarbageCollection() [all …]
|
/external/chromium_org/third_party/WebKit/Source/devtools/front_end/ |
D | externs.js | 395 indentLine: function(n, dir, aggressive) { }, argument
|
/external/ipsec-tools/src/racoon/ |
D | TODO | 32 guess phase 1 DH group (for aggressive mode, we cannot negotiate it)
|
/external/iproute2/doc/ |
D | arpd.sgml | 124 It is not default just to prevent occasional enabling of too aggressive
|
/external/okhttp/ |
D | CHANGELOG.md | 118 * Be more aggressive about testing pooled sockets before reuse. (thanks
|
/external/chromium_org/testing/gtest/ |
D | CMakeLists.txt | 79 # aggressive about warnings.
|
/external/ipsec-tools/src/racoon/doc/ |
D | README.gssapi | 74 * The various state functions for aggressive and main mode
|
/external/llvm/include/llvm/IR/ |
D | Intrinsics.td | 23 // these properties set. They are listed from the most aggressive (best to use 24 // if correct) to the least aggressive. If no property is set, the worst case
|
/external/chromium_org/third_party/brotli/src/ |
D | README | 100 The string representing the currently most aggressive optimization level is:
|
/external/llvm/test/Analysis/ScalarEvolution/ |
D | scev-aa.ll | 146 ; do aggressive analysis. Contrast this with BasicAA, which works by
|
/external/chromium_org/third_party/sqlite/src/test/ |
D | sort.test | 450 # Trouble reported on the mailing list. Check for overly aggressive
|
/external/eigen/doc/ |
D | TutorialMatrixClass.dox | 218 Finally, depending on circumstances, Eigen can also be more aggressive trying to vectorize
|
/external/llvm/test/Transforms/MemCpyOpt/ |
D | form-memset.ll | 223 ; More aggressive heuristic
|
/external/llvm/docs/ |
D | Vectorizers.rst | 425 $ clang -fslp-vectorize-aggressive file.c
|
123