HomeSort by relevance Sort by last modified time
    Searched full:precise (Results 401 - 425 of 1035) sorted by null

<<11121314151617181920>>

  /device/lge/hammerhead/
device.mk 102 PRODUCT_TAGS += dalvik.gc.type-precise
  /external/bison/src/
files.c 237 The precise -o name will be used for FTABLE. For other output
  /external/ceres-solver/include/ceres/
types.h 173 // precise choice of the non-linear conjugate gradient algorithm
  /external/chromium/base/
time_win.cc 11 // The default windows timer, GetSystemTimeAsFileTime is not very precise.
  /external/chromium/chrome/browser/resources/options/
language_list.js 123 // for content negotiation. To be more precise, the list will be used
  /external/chromium/net/base/
filter_unittest.cc 139 // was an html type. Note that it *should* be the case that a precise match
  /external/chromium_org/chrome/browser/resources/options/
language_list.js 106 // for content negotiation. To be more precise, the list will be used
  /external/chromium_org/chrome/installer/mac/
dmgdiffer.sh 119 # with a more precise status than would be possible here.
  /external/chromium_org/components/translate/language_detection/
language_detection_util.cc 161 // CLD2::CHINESE_T. This is technically more precise for the language
  /external/chromium_org/media/base/
sinc_resampler_unittest.cc 134 // The optimized Convolve methods are slightly more precise than Convolve_C(),
  /external/chromium_org/net/base/
filter_unittest.cc 139 // was an html type. Note that it *should* be the case that a precise match
  /external/chromium_org/net/proxy/
proxy_service.h 62 // The timer method is more precise and guarantees that polling happens when
  /external/chromium_org/net/quic/
quic_http_stream.cc 115 // TODO(rch): Can we be more precise about when to allocate
  /external/chromium_org/sync/engine/
commit_util.cc 51 // for a rough estimate of extensions activity, not an precise mapping of
  /external/chromium_org/third_party/WebKit/Source/platform/scroll/
ScrollView.h 181 // the entire widget hierarchy. It is up to the platform to decide what the precise definition
  /external/chromium_org/third_party/WebKit/Source/wtf/dtoa/
double-conversion.h 152 // For example the most precise representation of the double 9e59 equals
strtod.cc 350 // fall back to a more precise algorithm.
  /external/chromium_org/third_party/icu/source/common/unicode/
utrace.h 267 * - the precise formatting is up to the application!
  /external/chromium_org/third_party/protobuf/src/google/protobuf/io/
tokenizer.h 79 // precise descriptions. Whitespace and comments are skipped. By default,
  /external/chromium_org/third_party/re2/re2/
prog.h 317 // some cases be arbitrarily precise, so the caller gets to specify the
  /external/chromium_org/third_party/skia/src/pdf/
SkPDFTypes.cpp 163 // no more precise than an int. (Plus PDF doesn't support scientific
  /external/chromium_org/v8/src/ia32/
debug-ia32.cc 48 // for the precise return instructions sequence.
  /external/chromium_org/v8/src/
strtod.cc 351 // fall back to a more precise algorithm.
  /external/chromium_org/v8/src/x64/
debug-x64.cc 49 // for the precise return instructions sequence.
  /external/clang/include/clang/StaticAnalyzer/Core/PathSensitive/
ExplodedGraph.h 12 // See "Precise interprocedural dataflow analysis via graph reachability"

Completed in 561 milliseconds

<<11121314151617181920>>