Skip to content
  1. Jan 05, 2010
  2. Jan 03, 2010
  3. Dec 02, 2009
  4. Nov 10, 2009
  5. Nov 07, 2009
  6. Nov 05, 2009
  7. Oct 28, 2009
  8. Oct 27, 2009
  9. Oct 24, 2009
  10. Sep 02, 2009
  11. Jul 24, 2009
  12. May 09, 2009
  13. Jan 12, 2009
  14. Dec 07, 2008
  15. Dec 06, 2008
  16. Dec 05, 2008
    • Chris Lattner's avatar
      Make a few major changes to memdep and its clients: · 0e3d6337
      Chris Lattner authored
      1. Merge the 'None' result into 'Normal', making loads
         and stores return their dependencies on allocations as Normal.
      2. Split the 'Normal' result into 'Clobber' and 'Def' to
         distinguish between the cases when memdep knows the value is
         produced from when we just know if may be changed.
      3. Move some of the logic for determining whether readonly calls
         are CSEs into memdep instead of it being in GVN.  This still
         leaves verification that the arguments are hte same to GVN to
         let it know about value equivalences in different contexts.
      4. Change memdep's call/call dependency analysis to use 
         getModRefInfo(CallSite,CallSite) instead of doing something 
         very weak.  This only really matters for things like DSA, but
         someday maybe we'll have some other decent context sensitive
         analyses :)
      5. This reimplements the guts of memdep to handle the new results.
      6. This simplifies GVN significantly:
         a) readonly call CSE is slightly simpler
         b) I eliminated the "getDependencyFrom" chaining for load 
            elimination and load CSE doesn't have to worry about 
            volatile (they are always clobbers) anymore.
         c) GVN no longer does any 'lastLoad' caching, leaving it to 
            memdep.
      7. The logic in DSE is simplified a bit and sped up.  A potentially
         unsafe case was eliminated.
      
      llvm-svn: 60607
      0e3d6337
  17. Nov 29, 2008
  18. Nov 28, 2008
  19. Oct 01, 2008
    • Duncan Sands's avatar
      Factorize code: remove variants of "strip off · d65a4dae
      Duncan Sands authored
      pointer bitcasts and GEP's", and centralize the
      logic in Value::getUnderlyingObject.  The
      difference with stripPointerCasts is that
      stripPointerCasts only strips GEPs if all
      indices are zero, while getUnderlyingObject
      strips GEPs no matter what the indices are.
      
      llvm-svn: 56922
      d65a4dae
  20. Sep 04, 2008
  21. Jul 28, 2008
  22. May 13, 2008
  23. Apr 28, 2008
  24. Feb 04, 2008
Loading