| /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/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.
|
| D | 2000-11-18-EarlyDesignIdeas.txt | 10 portability and safety like the Java VM? Or shall we focus on the
|
| D | 2000-11-18-EarlyDesignIdeasResp.txt | 10 > portability and safety like the Java VM? Or shall we focus on the
173 you get safety and conservatism, and on the other you get degree of
|
| /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/jpeg/ |
| D | 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/mesa3d/docs/ |
| D | README.THREADS | 6 Thread safety was introduced in Mesa 2.6 by John Stone and
9 It was redesigned in Mesa 3.3 so that thread safety is
41 If you are interested in helping with thread safety work in Mesa
|
| D | libGL.txt | 49 libGL.so is thread safe. The overhead of thread safety for common,
51 safety for multi-threaded clients is significant. Each GL API call
|
| /external/owasp/sanitizer/lib/commons-codec-1.4/ |
| D | RELEASE-NOTES.txt | 33 o [CODEC-70] Thread safety and malicious code safety improvements.
|
| /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/clang/include/clang/Basic/ |
| D | DiagnosticGroups.td | 571 def TypeSafety : DiagGroup<"type-safety">;
617 def ThreadSafetyAttributes : DiagGroup<"thread-safety-attributes">;
618 def ThreadSafetyAnalysis : DiagGroup<"thread-safety-analysis">;
619 def ThreadSafetyPrecise : DiagGroup<"thread-safety-precise">;
620 def ThreadSafetyReference : DiagGroup<"thread-safety-reference">;
621 def ThreadSafetyNegative : DiagGroup<"thread-safety-negative">;
622 def ThreadSafety : DiagGroup<"thread-safety",
627 def ThreadSafetyVerbose : DiagGroup<"thread-safety-verbose">;
628 def ThreadSafetyBeta : DiagGroup<"thread-safety-beta">;
|
| /external/elfutils/src/ |
| D | configure.ac | 62 AC_ARG_ENABLE([thread-safety],
63 AS_HELP_STRING([--enable-thread-safety],
64 [enable thread safety of libraries EXPERIMENTAL]),
69 [AC_MSG_WARN([thread-safety is EXPERIMENTAL tests might fail.])])
|
| D | ChangeLog | 118 * configure.ac (--enable-thread-safety): Add AC_MSG_WARN experimental
261 --enable-thread-safety.
|
| /external/icu/icu4c/source/config/ |
| D | mh-irix | 26 ## Additional flags when building libraries with thread safety
|
| /external/libxml2/os400/libxmlrpg/ |
| D | parserInternals.rpgle | 21 * process. This is not a limitation of the parser but a safety
30 * This is not a limitation of the parser but a safety boundary feature,
40 * This is not a limitation of the parser but a safety boundary feature,
52 * This is not a limitation of the parser but a safety boundary feature,
|
| /external/mesa3d/src/gallium/state_trackers/vega/ |
| D | arc.c | 433 const double *safety; in estimate_error() local
435 safety = safety3; in estimate_error()
447 return rational_function(x, safety) * arc->a * exp(c0 + c1 * dEta); in estimate_error()
|
| /external/bison/tests/ |
| D | c++.at | 187 ## Exception safety. ##
190 AT_SETUP([[Exception safety]])
|
| /external/compiler-rt/lib/tsan/rtl/ |
| D | tsan_flags.inc | 39 "Report violations of async signal-safety "
|
| /external/webrtc/src/modules/audio_processing/aec/ |
| D | aec_core.c | 1381 const float safety = 0.99995f; in UpdateMetrics() local
1408 echo = aec->nearlevel.averagelevel - safety * aec->nearlevel.minlevel; in UpdateMetrics()
1441 safety * aec->linoutlevel.minlevel); in UpdateMetrics()
1469 safety * aec->nlpoutlevel.minlevel); in UpdateMetrics()
|
| /external/fio/ |
| D | README | 163 --readonly Turn on safety read-only checks, preventing
188 The --readonly option is an extra safety guard to prevent users from
191 safety net can be used as an extra precaution as --readonly will also
|
| /external/google-breakpad/src/common/mac/ |
| D | MachIPC.mm | 287 return KERN_INVALID_VALUE; // just for safety -- never should occur
|
| /external/libvpx/libvpx/vpx_ports/ |
| D | x86_abi_support.asm | 178 ; The Microsoft assembler tries to impose a certain amount of type safety in
|