| /external/apache-commons-math/src/main/java/org/apache/commons/math/ode/ |
| D | MultistepIntegrator.java | 82 private double safety; field in MultistepIntegrator
281 return safety; in getSafety()
287 public void setSafety(final double safety) { in setSafety() argument
288 this.safety = safety; in setSafety()
296 … return FastMath.min(maxGrowth, FastMath.max(minReduction, safety * FastMath.pow(error, exp))); in computeStepGrowShrinkFactor()
|
| /external/apache-commons-math/src/main/java/org/apache/commons/math/ode/nonstiff/ |
| D | EmbeddedRungeKuttaIntegrator.java | 87 private double safety; field in EmbeddedRungeKuttaIntegrator
180 return safety; in getSafety()
186 public void setSafety(final double safety) { in setSafety() argument
187 this.safety = safety; in setSafety()
294 FastMath.max(minReduction, safety * FastMath.pow(error, exp))); in integrate()
318 … FastMath.min(maxGrowth, FastMath.max(minReduction, safety * FastMath.pow(error, exp))); in integrate()
|
| /external/webrtc/webrtc/modules/audio_device/mac/portaudio/ |
| D | pa_memorybarrier.h | 93 # warning For SMP safety, you should fix this.
98 …his system. You can still compile by defining ALLOW_SMP_DANGERS, but SMP safety will not be guaran…
120 # warning For SMP safety, you should fix this.
125 …his system. You can still compile by defining ALLOW_SMP_DANGERS, but SMP safety will not be guaran…
|
| /external/clang/docs/ |
| D | ThreadSafetyAnalysis.rst | 16 Thread safety analysis works very much like a type system for multi-threaded
69 analysis issues a warning. Thread safety analysis is not inter-procedural, so
85 To run the analysis, simply compile with the ``-Wthread-safety`` flag, e.g.
89 clang -c -Wthread-safety example.cpp
99 Thread safety analysis provides a way of protecting *resources* with
141 The thread safety analysis uses attributes to declare threading constraints.
147 For historical reasons, prior versions of thread safety used macro names that
314 turns off thread safety checking for that method. It provides an escape hatch
438 * ``-Wthread-safety``: Umbrella flag which turns on the following three:
440 + ``-Wthread-safety-attributes``: Sanity checks on attribute syntax.
[all …]
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2001-01-31-UniversalIRIdea.txt | 13 static and runtime optimization; some higher-level like type-safety and
21 machine-independent features like type-safety and access safety should be
32 without type-safety as the intermediate representation.
|
| /external/swiftshader/third_party/LLVM/docs/HistoricalNotes/ |
| D | 2001-01-31-UniversalIRIdea.txt | 13 static and runtime optimization; some higher-level like type-safety and
21 machine-independent features like type-safety and access safety should be
32 without type-safety as the intermediate representation.
|
| /external/clang/test/SemaObjC/ |
| D | warn-thread-safety-analysis.m | 1 // RUN: %clang_cc1 -fsyntax-only -verify -Wthread-safety -Wthread-safety-beta -Wno-objc-root-class …
|
| D | block-type-safety.m | 2 // test for block type safety.
89 // strict type safety requires this:
|
| /external/owasp/sanitizer/lib/commons-codec-1.4/ |
| D | RELEASE-NOTES.txt | 33 o [CODEC-70] Thread safety and malicious code safety improvements.
|
| /external/swiftshader/third_party/LLVM/test/Linker/ |
| D | 2003-08-23-RecursiveOpaqueTypeResolve.ll | 1 ; It's a bad idea to go recursively traipsing through types without a safety
|
| /external/llvm/test/Linker/ |
| D | 2003-08-23-RecursiveOpaqueTypeResolve.ll | 1 ; It's a bad idea to go recursively traipsing through types without a safety
|
| /external/autotest/test_suites/ |
| D | control.sanity | 17 on the safety checks built into the provisioning code to identify bad builds.
|
| /external/protobuf/objectivec/google/protobuf/ |
| D | Empty.pbobjc.m | 21 // about thread safety of the singleton.
|
| D | SourceContext.pbobjc.m | 21 // about thread safety of the singleton.
|
| D | FieldMask.pbobjc.m | 21 // about thread safety of the singleton.
|
| D | Duration.pbobjc.m | 21 // about thread safety of the singleton.
|
| D | Any.pbobjc.m | 21 // about thread safety of the singleton.
|
| D | Timestamp.pbobjc.m | 21 // about thread safety of the singleton.
|
| /external/llvm/docs/ |
| D | FaultMaps.rst | 13 are required for safety but never fail in practice. In such cases, it
16 exploited by folding such safety checks into operations that can be
|
| /external/syslinux/com32/lib/libpng/ |
| D | TODO | 20 Should we always malloc 2^bit_depth PLTE/tRNS/hIST entries for safety?
|
| /external/clang/include/clang/Basic/ |
| D | DiagnosticGroups.td | 615 def TypeSafety : DiagGroup<"type-safety">;
666 def ThreadSafetyAttributes : DiagGroup<"thread-safety-attributes">;
667 def ThreadSafetyAnalysis : DiagGroup<"thread-safety-analysis">;
668 def ThreadSafetyPrecise : DiagGroup<"thread-safety-precise">;
669 def ThreadSafetyReference : DiagGroup<"thread-safety-reference">;
670 def ThreadSafetyNegative : DiagGroup<"thread-safety-negative">;
671 def ThreadSafety : DiagGroup<"thread-safety",
676 def ThreadSafetyVerbose : DiagGroup<"thread-safety-verbose">;
677 def ThreadSafetyBeta : DiagGroup<"thread-safety-beta">;
|
| /external/elfutils/ |
| D | configure.ac | 58 AC_ARG_ENABLE([thread-safety],
59 AS_HELP_STRING([--enable-thread-safety],
60 [enable thread safety of libraries EXPERIMENTAL]),
65 [AC_MSG_WARN([thread-safety is EXPERIMENTAL tests might fail.])])
483 Experimental thread safety : ${use_locks}
|
| /external/swiftshader/third_party/LLVM/test/CodeGen/CellSPU/ |
| D | loads.ll | 26 ; we need to have some instruction to move the result to safety.
|
| /external/libmojo/mojo/public/cpp/ |
| D | README.md | 8 wrappers provide increased convenience and/or type-safety.
|
| /external/python/cpython2/Doc/c-api/ |
| D | bytearray.rst | 78 These macros trade safety for speed and they don't check pointers.
|