Home
last modified time | relevance | path

Searched refs:assumption (Results 1 – 25 of 85) sorted by relevance

1234

/external/clang/lib/StaticAnalyzer/Core/
DSimpleConstraintManager.cpp77 bool assumption) { in assume() argument
78 state = assumeAux(state, cond, assumption); in assume()
80 return SU->processAssume(state, cond, assumption); in assume()
120 bool assumption) { in assume() argument
121 state = assumeAux(state, cond, assumption); in assume()
123 return SU->processAssume(state, cond, assumption); in assume()
/external/junit/src/org/junit/internal/
DAssumptionViolatedException.java21 public AssumptionViolatedException(String assumption) { in AssumptionViolatedException() argument
22 this(assumption, null); in AssumptionViolatedException()
/external/elfutils/
DREADME6 assumption is in sight this is believed to be a worthwhile optimization.
/external/clang/lib/StaticAnalyzer/Checkers/
DIdempotentOperationChecker.cpp101 BinaryOperatorData() : assumption(Possible) {} in BinaryOperatorData()
103 Assumption assumption; member
121 Assumption &A = Data.assumption; in checkPreStmt()
356 const Assumption &A = Data.assumption; in checkEndAnalysis()
/external/clang/include/clang/StaticAnalyzer/Core/BugReporter/
DBugReporterVisitor.h142 TrackConstraintBRVisitor(DefinedSVal constraint, bool assumption) in TrackConstraintBRVisitor() argument
143 : Constraint(constraint), Assumption(assumption), IsSatisfied(false), in TrackConstraintBRVisitor()
/external/chromium_org/v8/
DDEPS3 # all paths in here must match this assumption.
/external/eigen/doc/
DD03_WrongStackAlignment.dox3 /** \page TopicWrongStackAlignment Compiler making a wrong assumption on stack alignment
22 The problem is that, in some particular cases, this assumption can be wrong on Windows, where the s…
DD11_UnalignedArrayAssert.dox82 \section c4 Cause 4: Compiler making a wrong assumption on stack alignment (for instance GCC on Win…
94 … separate page: \ref TopicWrongStackAlignment "Compiler making a wrong assumption on stack alignme…
/external/libvpx/libvpx/vp8/common/ppc/
Dcopy_altivec.asm19 ;# Make the assumption that input will not be aligned,
/external/bison/m4/
Dmode_t.m417 dnl and to itself otherwise. This assumption is not guaranteed by the ISO C
/external/llvm/test/Transforms/LoopVectorize/
Dinfiniteloop.ll11 ; induction variable. This is not a valid assumption:
/external/clang/include/clang/StaticAnalyzer/Core/PathSensitive/
DSubEngine.h106 SVal cond, bool assumption) = 0;
DProgramState.h178 ProgramStateRef assume(DefinedOrUnknownSVal cond, bool assumption) const;
190 bool assumption,
DExprEngine.h266 ProgramStateRef processAssume(ProgramStateRef state, SVal cond,bool assumption);
/external/llvm/test/CodeGen/ARM/
Dsjlj-prepare-critical-edge.ll2 ; Just make sure no one tries to make the assumption that the normal edge of an
/external/llvm/test/Transforms/GVN/
Dpre-single-pred.ll9 ; Now that that faulty assumption is corrected, test that we DON'T incorrectly
/external/chromium/chrome/browser/ui/cocoa/extensions/
Dextension_view_mac.mm70 // TODO(andybons): Verify this assumption and look into WebCore's
/external/clang/include/clang/StaticAnalyzer/Core/
DChecker.h396 bool assumption) { in _evalAssume() argument
397 return ((const CHECKER *)checker)->evalAssume(state, cond, assumption); in _evalAssume()
/external/llvm/test/CodeGen/SystemZ/
Daddr-02.ll2 ; The assumption here is that we should match complex addresses where
/external/valgrind/main/docs/internals/
Dwhy-no-libc.txt36 both designed with the assumption that they alone will be talking to
/external/chromium_org/third_party/yasm/source/patched-yasm/libyasm/tests/
Dopt-gvmat64.asm90 ;;; assumption that the compiler will dword-align the fields. (Thus,
/external/libexif/auto-m4/
Dlib-prefix.m419 dnl to access previously installed libraries. The basic assumption is that
/external/chromium_org/third_party/yasm/source/patched-yasm/m4/
Dlib-prefix.m417 dnl to access previously installed libraries. The basic assumption is that
/external/zlib/src/contrib/masmx86/
Dmatch686.asm142 ;;; assumption that the compiler will dword-align the fields. (Thus,
/external/srtp/
DREADME145 tag can be written to the end of that packet. If this assumption

1234