Searched
full:significant (Results
801 -
825 of
2519) sorted by null
<<31323334353637383940>>
/external/aac/libSYS/include/ |
wav_file.h | 215 * \param nSigBits Amount of significant bits of each nBufBits in sampleBuffer.
|
/external/bison/src/ |
system.h | 80 suppressing Code is unlikely to offer any significant improvement in
|
/external/bluetooth/bluedroid/embdrv/sbc/decoder/srce/ |
synthesis-dct8.c | 60 * @return A signed 32-bit value corresponding to the 32 most significant bits
|
/external/bluetooth/bluedroid/stack/btm/ |
btm_ble_int.h | 82 #define BLE_RESOLVE_ADDR_MSB 0x40 /* most significant bit, bit7, bit6 is 01 to be resolvable random */
|
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/asn1/x509/ |
GeneralName.java | 100 * specified in RFC 791 [RFC 791]. The least significant bit (LSB) of
|
/external/chromium_org/chrome/browser/ui/omnibox/ |
omnibox_popup_model.cc | 72 // However, if this makes the contents too narrow to show a significant
|
/external/chromium_org/chrome/browser/ui/webui/options/ |
create_profile_handler.cc | 316 // profile shouldn't take significant time, and it can easily be deleted
|
/external/chromium_org/chrome/common/extensions/docs/templates/articles/ |
event_pages.html | 22 performance advantages are significant, especially on low-power devices. Please
|
sandboxingEval.html | 193 significant security risk, as even a complete compromise of the sandboxed code
|
/external/chromium_org/chrome/installer/linux/debian/ |
build.sh | 21 # have any type of "significant/visible changes" log that we could use for this?
|
/external/chromium_org/components/invalidation/ |
ticl_invalidation_service.cc | 45 // has no significant state, -1 to never discard.
|
/external/chromium_org/content/browser/loader/ |
redirect_to_file_resource_handler.cc | 32 // principled approach would require significant refactoring, however, so for
|
/external/chromium_org/google_apis/gcm/engine/ |
registration_request_unittest.cc | 50 // has no significant state, -1 to never discard.
|
/external/chromium_org/media/cast/net/rtcp/ |
rtcp.cc | 270 // contributes a very significant source of error here. Determine whether
|
/external/chromium_org/net/dns/ |
dns_protocol.h | 94 // In MDns the most significant bit of the rrclass is designated as the
|
/external/chromium_org/net/http/ |
http_security_headers.cc | 151 // 1. The order of appearance of directives is not significant.
|
/external/chromium_org/ppapi/api/ |
ppp_instance.idl | 143 * region. The time saved doing partial paints is usually not significant and
|
/external/chromium_org/testing/gtest/include/gtest/ |
gtest-death-test.h | 148 // death test, which already incurs significant overhead by launching
|
/external/chromium_org/third_party/WebKit/Source/bindings/scripts/ |
compute_interfaces_info_overall.py | 73 moving or deleting files (hence requiring a full rebuild anyway) or significant
|
/external/chromium_org/third_party/WebKit/public/web/ |
WebSettings.h | 74 // a significant action on the user?s part. e.g. hover on ?long press?.
|
/external/chromium_org/third_party/bintrees/bintrees/ |
avltree.py | 25 # black trees or Andersson trees are a better solution. If there is a significant
|
/external/chromium_org/third_party/fontconfig/include/ |
config.h | 321 significant byte first (like Motorola and SPARC, unlike Intel). */
|
/external/chromium_org/third_party/icu/source/common/ |
uprops.h | 81 * (only one significant decimal digit)
|
/external/chromium_org/third_party/icu/source/i18n/unicode/ |
uformattable.h | 146 * if there are additional significant digits than fit in a double type,
|
unum.h | 855 /** Use significant digits 858 /** Minimum significant digits 861 /** Maximum significant digits [all...] |
Completed in 1161 milliseconds
<<31323334353637383940>>