/external/libcxx/test/utilities/memory/util.dynamic.safety/ |
Android.mk | 17 test_makefile := external/libcxx/test/utilities/memory/util.dynamic.safety/Android.mk 19 test_name := utilities/memory/util.dynamic.safety/get_pointer_safety 23 test_name := utilities/memory/util.dynamic.safety/declare_no_pointers 27 test_name := utilities/memory/util.dynamic.safety/declare_reachable
|
/external/chromium_org/third_party/webrtc/modules/audio_device/mac/portaudio/ |
pa_memorybarrier.h | 93 # warning For SMP safety, you should fix this. 98 # error Memory barriers are not defined on this system. You can still compile by defining ALLOW_SMP_DANGERS, but SMP safety will not be guaranteed. 120 # warning For SMP safety, you should fix this. 125 # error Memory barriers are not defined on this system. You can still compile by defining ALLOW_SMP_DANGERS, but SMP safety will not be guaranteed.
|
/external/chromium_org/third_party/angle/src/compiler/preprocessor/ |
generate_parser.sh | 27 patch --silent --forward < 64bit-tokenizer-safety.patch
|
/external/chromium_org/third_party/angle/src/compiler/translator/ |
generate_parser.sh | 28 patch --silent --forward < 64bit-lexer-safety.patch
|
/art/build/ |
Android.common_build.mk | 259 # Enable thread-safety for GCC 4.6, and clang, but not for GCC 4.7 or later where this feature was 260 # removed. Warn when -Wthread-safety is not used. 262 ART_TARGET_CFLAGS += -Wthread-safety 264 # FIXME: add -Wthread-safety when the problem is fixed 268 # Warn if -Wthread-safety is not supported and not doing a top-level or 'mma' build. 271 $(info Using target GCC $(TARGET_GCC_VERSION) disables thread-safety checks.) 275 # We compile with GCC 4.6 or clang on the host, both of which support -Wthread-safety. 276 ART_HOST_CFLAGS += -Wthread-safety
|
/external/jpeg/ |
jmemdosa.asm | 46 push si ; save all registers for safety 81 push si ; save all registers for safety 113 push si ; save all registers for safety 147 push si ; save all registers for safety 185 push si ; save all registers for safety 223 push si ; save all registers for safety 266 push si ; save all registers for safety 303 push si ; save all registers for safety 347 push si ; save all registers for safety
|
/external/qemu/distrib/jpeg-6b/ |
jmemdosa.asm | 46 push si ; save all registers for safety 81 push si ; save all registers for safety 113 push si ; save all registers for safety 147 push si ; save all registers for safety 185 push si ; save all registers for safety 223 push si ; save all registers for safety 266 push si ; save all registers for safety 303 push si ; save all registers for safety 347 push si ; save all registers for safety
|
/prebuilts/eclipse/maven/apache-maven-3.2.1/lib/ |
jsoup-1.7.2.jar | |
/external/e2fsprogs/lib/blkid/ |
tag.c | 266 * library, and I really don't like the tradeoff of type-safety for
|
/external/chromium_org/third_party/mesa/src/src/gallium/state_trackers/vega/ |
arc.c | 80 /* safety factor to convert the "best" error approximation 433 const double *safety; local 435 safety = safety3; 447 return rational_function(x, safety) * arc->a * exp(c0 + c1 * dEta);
|
/external/mesa3d/src/gallium/state_trackers/vega/ |
arc.c | 80 /* safety factor to convert the "best" error approximation 433 const double *safety; local 435 safety = safety3; 447 return rational_function(x, safety) * arc->a * exp(c0 + c1 * dEta);
|
/external/chromium_org/third_party/webrtc/modules/audio_processing/aec/ |
aec_core.c | 1577 const float safety = 0.99995f; local [all...] |
/external/webrtc/src/modules/audio_processing/aec/ |
aec_core.c | 1381 const float safety = 0.99995f; local [all...] |
/external/chromium_org/native_client_sdk/src/doc/ |
faq.rst | 389 How does Google know that the safety measures in Native Client are sufficient?
|
/external/chromium_org/remoting/webapp/ |
host_screen.js | 233 // Hack to force JSCompiler type-safety.
|
/external/chromium_org/third_party/libvpx/source/libvpx/vpx_ports/ |
x86_abi_support.asm | 178 ; The Microsoft assembler tries to impose a certain amount of type safety in
|
/external/libvpx/libvpx/vpx_ports/ |
x86_abi_support.asm | 178 ; The Microsoft assembler tries to impose a certain amount of type safety in
|
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/vpx_ports/ |
x86_abi_support.asm | 178 ; The Microsoft assembler tries to impose a certain amount of type safety in
|
/external/libunwind/doc/ |
libunwind.tex | 235 \section{Thread- and Signal-Safety} 243 To ensure thread-safety, some \Prog{libunwind} routines may have to
|
/external/stlport/ |
configure.bat | 536 echo Removing thread safety support
|
/external/elfutils/0.153/ |
configure | [all...] |
/external/chromium_org/third_party/libvpx/source/libvpx/tools/ |
cpplint.py | [all...] |
/external/libvpx/libvpx/tools/ |
cpplint.py | [all...] |
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/tools/ |
cpplint.py | [all...] |
/external/chromium_org/third_party/icu/source/ |
configure | [all...] |