Skip to content
  1. Jan 31, 2012
  2. Jan 30, 2012
  3. Jan 29, 2012
  4. Jan 28, 2012
  5. Jan 27, 2012
  6. Jan 26, 2012
  7. Jan 25, 2012
  8. Jan 24, 2012
  9. Jan 23, 2012
  10. Jan 20, 2012
    • David Blaikie's avatar
      More dead code removal (using -Wunreachable-code) · 46a9f016
      David Blaikie authored
      llvm-svn: 148578
      46a9f016
    • Andrew Trick's avatar
      Handle a corner case with IV chain collection with bailout instead of assert. · b9c822ab
      Andrew Trick authored
      Fixes PR11783: bad cast to AddRecExpr.
      
      llvm-svn: 148572
      b9c822ab
    • Kostya Serebryany's avatar
      Extend Attributes to 64 bits · a5054ad2
      Kostya Serebryany authored
      Problem: LLVM needs more function attributes than currently available (32 bits).
      One such proposed attribute is "address_safety", which shows that a function is being checked for address safety (by AddressSanitizer, SAFECode, etc).
      
      Solution:
      - extend the Attributes from 32 bits to 64-bits
      - wrap the object into a class so that unsigned is never erroneously used instead
      - change "unsigned" to "Attributes" throughout the code, including one place in clang.
      - the class has no "operator uint64 ()", but it has "uint64_t Raw() " to support packing/unpacking.
      - the class has "safe operator bool()" to support the common idiom:  if (Attributes attr = getAttrs()) useAttrs(attr);
      - The CTOR from uint64_t is marked explicit, so I had to add a few explicit CTOR calls
      - Add the new attribute "address_safety". Doing it in the same commit to check that attributes beyond first 32 bits actually work.
      - Some of the functions from the Attribute namespace are worth moving inside the class, but I'd prefer to have it as a separate commit.
      
      Tested:
      "make check" on Linux (32-bit and 64-bit) and Mac (10.6)
      built/run spec CPU 2006 on Linux with clang -O2.
      
      
      This change will break clang build in lib/CodeGen/CGCall.cpp.
      The following patch will fix it.
      
      llvm-svn: 148553
      a5054ad2
    • Andrew Trick's avatar
      SCEVExpander fixes. Affects LSR and indvars. · c908b43d
      Andrew Trick authored
      LSR has gradually been improved to more aggressively reuse existing code, particularly existing phi cycles. This exposed problems with the SCEVExpander's sloppy treatment of its insertion point. I applied some rigor to the insertion point problem that will hopefully avoid an endless bug cycle in this area. Changes:
      
      - Always used properlyDominates to check safe code hoisting.
      
      - The insertion point provided to SCEV is now considered a lower bound. This is usually a block terminator or the use itself. Under no cirumstance may SCEVExpander insert below this point.
      
      - LSR is reponsible for finding a "canonical" insertion point across expansion of different expressions.
      
      - Robust logic to determine whether IV increments are in "expanded" form and/or can be safely hoisted above some insertion point.
      
      Fixes PR11783: SCEVExpander assert.
      
      llvm-svn: 148535
      c908b43d
  11. Jan 19, 2012
  12. Jan 18, 2012
  13. Jan 17, 2012
Loading