Skip to content
  1. May 28, 2009
    • Bill Wendling's avatar
      "The instructions MMX_PSADBWrm and MMX_PSADBWrr have opcode 0b11100000 (e0), but · 0feb0e60
      Bill Wendling authored
      the Intel manual (screenshot) says it should be 0b11110110 (f6).  The existing
      encoding causes a disassembly conflict with MMX_PAVGBrm, which really should be
      0f e0."
      
      Patch by Sean Callanan!
      
      llvm-svn: 72508
      0feb0e60
    • Evan Cheng's avatar
      Added optimization that narrow load / op / store and the 'op' is a bit... · a9cda8ab
      Evan Cheng authored
      Added optimization that narrow load / op / store and the 'op' is a bit twiddling instruction and its second operand is an immediate. If bits that are touched by 'op' can be done with a narrower instruction, reduce the width of the load and store as well. This happens a lot with bitfield manipulation code.
      e.g.
      orl     $65536, 8(%rax)
      =>
      orb     $1, 10(%rax)
      
      Since narrowing is not always a win, e.g. i32 -> i16 is a loss on x86, dag combiner consults with the target before performing the optimization.
      
      llvm-svn: 72507
      a9cda8ab
  2. May 27, 2009
  3. May 26, 2009
  4. May 25, 2009
Loading