Skip to content
  1. Nov 10, 2009
  2. Sep 09, 2009
  3. Aug 28, 2009
  4. Aug 22, 2009
    • Ted Kremenek's avatar
      Remove 'SelfRegion' field from both BasicStoreManager and RegionStoreManager. · 608677a2
      Ted Kremenek authored
      SelfRegion represented the object bound to 'self' (when analyzing Objective-C
      methods) upon entry to a method. Having this region stored on the side ignores
      the current stack frame that we might be analyzing (among other things), and is
      a problem for interprocedural analysis.
      
      For RegionStoreManager, the value for SelfRegion is just lazily created.
      
      For BasicStoreManager, the value for SelfRegion is bound eagerly to 'self', but
      no explicit tracking of SelfRegion on the side is made.
      
      As part of this change, remove the restriction in BasicStoreManager that we only
      track ivars for 'self'. This shouldn't actually change anything in terms of
      precision, and simplifies the logic.
      
      llvm-svn: 79694
      608677a2
    • Ted Kremenek's avatar
  5. Aug 01, 2009
    • Ted Kremenek's avatar
      This is a fairly large patch, which resulted from a cascade of changes · 1f22aa74
      Ted Kremenek authored
      made to RegionStore (and related classes) in order to handle some
      analyzer failures involving casts and manipulation of symbolic memory.
      
      The root of the change is in StoreManager::CastRegion().  Instead of
      using ad hoc heuristics to decide when to layer an ElementRegion on a
      casted MemRegion, we now always layer an ElementRegion when the cast
      type is different than the original type of the region.  This carries
      the current cast information associated with a region around without
      resorting to the error prone recording of "casted types" in GRState.
      
      Along with this new policy of layering ElementRegions, I added a new
      algorithm to strip away existing ElementRegions when they simply
      represented casts of a base memory object.  This algorithm computes
      the raw "byte offset" that an ElementRegion represents from the base
      region, and allows the new ElementRegion to be based off that offset.
      The added benefit is that this naturally handles a series of casts of
      a MemRegion without building up a set of redundant ElementRegions
      (thus canonicalizing the region view).
      
      Other related changes that cascaded from this one (as tests were
      failing in RegionStore):
      
      - Revamped RegionStoreManager::InvalidateRegion() to completely remove
        all bindings and default values from a region and all subregions.
        Now invalidated fields are not bound directly to new symbolic
        values; instead the base region has a "default" symbol value from
        which "derived symbols" can be created.  The main advantage of this
        approach is that it allows us to invalidate a region hierarchy and
        then lazily instantiate new values no matter how deep the hierarchy
        went (i.e., regardless of the number of field accesses,
        e.g. x->f->y->z->...).  The previous approach did not do this.
      
      - Slightly reworked RegionStoreManager::RemoveDeadBindings() to also
        incorporate live symbols and live regions that do not have direct
        bindings but also have "default values" used for lazy instantiation.
        The changes to 'InvalidateRegion' revealed that these were necessary
        in order to achieve lazy instantiation of values in the region store
        with those bindings being removed too early.
      
      - The changes to InvalidateRegion() and RemoveDeadBindings() revealed
        a serious bug in 'getSubRegionMap()' where not all region -> subregion
        relationships involved in actually bindings (explicit and implicit)
        were being recorded.  This has been fixed by using a worklist algorithm
        to iteratively fill in the region map.
      
      - Added special support to RegionStoreManager::Bind()/Retrieve() to handle
        OSAtomicCompareAndSwap in light of the new 'CastRegion' changes and the
        layering of ElementRegions.
      
      - Fixed a bug in SymbolReaper::isLive() where derived symbols were not
        being marked live if the symbol they were derived from was also live.
        This fix was critical for getting lazy instantiation in RegionStore
        to work.
      
      - Tidied up the implementation of ValueManager::getXXXSymbolVal() methods
        to use SymbolManager::canSymbolicate() to decide whether or not a
        symbol should be symbolicated.
      
      - 'test/Analysis/misc-ps-xfail.m' now passes; that test case has been
        moved to 'test/Analysis/misc-ps.m'.
      
      - Tweaked some pretty-printing of MemRegions, and implemented
        'ElementRegion::getRawOffset()' for use with the CastRegion changes.
      
      llvm-svn: 77782
      1f22aa74
  6. Jul 29, 2009
  7. Jul 19, 2009
  8. Jul 16, 2009
    • Ted Kremenek's avatar
      Move RegionStoreManager over to using new · c7b1dade
      Ted Kremenek authored
      ValueManager::makeArrayIndex()/convertArrayIndex() methods.  This
      handles yet another crash case when reasoning about array indices of
      different bitwidth and signedness.
      
      llvm-svn: 75884
      c7b1dade
  9. Jul 14, 2009
  10. Jul 10, 2009
  11. Jul 03, 2009
  12. Jul 02, 2009
  13. Jun 30, 2009
    • Chris Lattner's avatar
      Key decisions about 'bool' vs '_Bool' to be based on a new flag in langoptions. · c61089a6
      Chris Lattner authored
      This is simple enough, but then I thought it would be nice to make PrintingPolicy
      get a LangOptions so that various things can key off "bool" and "C++" independently.
      This spiraled out of control.  There are many fixme's, but I think things are slightly
      better than they were before.
      
      One thing that can be improved: CFG should probably have an ASTContext pointer in it,
      which would simplify its clients.
      
      llvm-svn: 74493
      c61089a6
  14. Jun 23, 2009
  15. Jun 16, 2009
  16. May 09, 2009
    • Zhongxing Xu's avatar
      rename: MemRegion: · 8038f7b3
      Zhongxing Xu authored
       RValueType => ObjectType
       LValueType => LocationType
      
      No functionality change.
      
      llvm-svn: 71304
      8038f7b3
  17. May 06, 2009
  18. May 04, 2009
    • Ted Kremenek's avatar
      Per conversations with Zhongxing, add an 'element type' to · 02e50896
      Ted Kremenek authored
      ElementRegion.  I also removed 'ElementRegion::getArrayRegion',
      although we may need to add this back.
      
      This breaks a few test cases with RegionStore:
      - 'array-struct.c' triggers an infinite recursion in RegionStoreManager.  Need to investigate.
      - misc-ps.m triggers a failure with RegionStoreManager as we now get the diagnostic:
        'Line 159: Uninitialized or undefined return value returned to caller.'
        
      There were a bunch of places that needed to be edit
      RegionStoreManager, and we may not be passing all the correct 'element
      types' down from GRExprEngine.
      
      Zhongxing: When you get a chance, could you review this?  I could have
      easily screwed up something basic in RegionStoreManager.
      
      llvm-svn: 70830
      02e50896
  19. Apr 29, 2009
  20. Apr 21, 2009
  21. Apr 11, 2009
  22. Apr 10, 2009
    • Zhongxing Xu's avatar
      Add prototype for CodeTextRegion. · 1aced0c9
      Zhongxing Xu authored
      A CodeTextRegion wraps two kinds of data: FunctionDecl* or SymbolRef. 
      The latter comes from the symbolic function pointer that are generated from
      function calls or input data.
      
      llvm-svn: 68777
      1aced0c9
Loading