Skip to content
  1. Oct 04, 2008
    • Ted Kremenek's avatar
      This is a big patch, but the functionality change is small and the rest of the... · 5ca90a24
      Ted Kremenek authored
      This is a big patch, but the functionality change is small and the rest of the patch consists of deltas due to API changes.
      
      This patch overhauls the "memory region" abstraction that was prototyped (but never really used) as part of the Store.h.  This patch adds MemRegion.h and MemRegion.cpp, which defines the class MemRegion and its subclasses.  This classes serve to define an abstract representation of memory, with regions being layered on other regions to to capture the relationships between fields and variables, variables and the address space they are allocated in, and so on.  
      
      The main motivation of this patch is that key parts of the analyzer assumed that all value bindings were to VarDecls.  In the future this won't be the case, and this patch removes lval::DeclVal and replaces it with lval::MemRegionVal.  Now all pieces of the analyzer must reason about abstract memory blocks instead of just variables.
      
      There should be no functionality change from this patch, but it opens the door for significant improvements to the analyzer such as field-sensitivity and object-sensitivity, both which were on hold until the memory abstraction got generalized.
      
      The memory region abstraction also allows type-information to literally be affixed to a memory region.  This will allow the some now redundant logic to be removed from the retain/release checker.
      
      llvm-svn: 57042
      5ca90a24
  2. Sep 19, 2008
    • Ted Kremenek's avatar
      Fixed logic error in BasicConstraintManager pointed out by Zhongxing Xu. · 34bfd8a4
      Ted Kremenek authored
      For checking if a symbol >= value, we need to check if symbol == value || symbol
      > value. When checking symbol > value and we know that symbol != value, the path
      is infeasible only if value == maximum integer.
      
      For checking if a symbol <= value, we need to check if symbol == value || symbol
      < value. When checking symbol < value and we know that symbol != value, the path
      is infeasible only if value == minimum integer.
      
      Updated test case exercising this logic: we only prune paths if the values are
      unsigned.
      
      llvm-svn: 56354
      34bfd8a4
    • Zhongxing Xu's avatar
      Add an omitted case for AssumeSymInt. · a8e88ecd
      Zhongxing Xu authored
      llvm-svn: 56334
      a8e88ecd
  3. Sep 17, 2008
  4. Aug 30, 2008
  5. Aug 29, 2008
  6. Aug 27, 2008
Loading