Skip to content
  1. Nov 29, 2008
    • Bill Wendling's avatar
    • Chris Lattner's avatar
      Now that DepType is private, we can start cleaning up some of its uses: · e4d32791
      Chris Lattner authored
      Document the Dirty value more precisely, use it for the uninitialized
      DepResultTy value.  Change reverse mappings to be from an instruction*
      instead of DepResultTy, and stop tracking other forms.  This makes it more
      clear that we only care about the instruction cases.
      
      Eliminate a DepResultTy,bool pair by using Dirty in the local case as well,
      shrinking the map and simplifying the code.
      
      This speeds up GVN by ~3% on 403.gcc.
      
      llvm-svn: 60232
      e4d32791
    • Chris Lattner's avatar
      Introduce and use a new MemDepResult class to hold the results of a memdep · 7f9c8a0f
      Chris Lattner authored
      query.  This makes it crystal clear what cases can escape from MemDep that
      the clients have to handle.  This also gives the clients a nice simplified
      interface to it that is easy to poke at.
      
      This patch also makes DepResultTy and MemoryDependenceAnalysis::DepType
      private, yay.
      
      llvm-svn: 60231
      7f9c8a0f
    • Chris Lattner's avatar
      Reimplement the internal abstraction used by MemDep in terms · de04e117
      Chris Lattner authored
      of a pointer/int pair instead of a manually bitmangled pointer.
      This forces clients to think a little more about checking the 
      appropriate pieces and will be useful for internal 
      implementation improvements later.
      
      I'm not particularly happy with this.  After going through this
      I don't think that the clients of memdep should be exposed to
      the internal type at all.  I'll fix this in a subsequent commit.
      
      This has no functionality change.
      
      llvm-svn: 60230
      de04e117
  2. Nov 28, 2008
  3. Nov 27, 2008
Loading