Skip to content
  1. Dec 05, 2007
  2. Dec 04, 2007
  3. Dec 03, 2007
  4. Dec 02, 2007
  5. Dec 01, 2007
  6. Nov 30, 2007
  7. Nov 29, 2007
  8. Nov 28, 2007
  9. Nov 27, 2007
  10. Nov 24, 2007
    • Chris Lattner's avatar
      cab915f9
    • Chris Lattner's avatar
      Implement support for custom legalization in DAGTypeLegalizer::ExpandOperand. · 6e364189
      Chris Lattner authored
      Improve a comment.
      Unbreak Duncan's carefully written path compression where I didn't realize
      what was happening!
      
      llvm-svn: 44301
      6e364189
    • Chris Lattner's avatar
      Several changes: · f81d5886
      Chris Lattner authored
      1) Change the interface to TargetLowering::ExpandOperationResult to 
         take and return entire NODES that need a result expanded, not just
         the value.  This allows us to handle things like READCYCLECOUNTER,
         which returns two values.
      2) Implement (extremely limited) support in LegalizeDAG::ExpandOp for MERGE_VALUES.
      3) Reimplement custom lowering in LegalizeDAGTypes in terms of the new
         ExpandOperationResult.  This makes the result simpler and fully 
         general.
      4) Implement (fully general) expand support for MERGE_VALUES in LegalizeDAGTypes.
      5) Implement ExpandOperationResult support for ARM f64->i64 bitconvert and ARM
         i64 shifts, allowing them to work with LegalizeDAGTypes.
      6) Implement ExpandOperationResult support for X86 READCYCLECOUNTER and FP_TO_SINT,
         allowing them to work with LegalizeDAGTypes.
      
      LegalizeDAGTypes now passes several more X86 codegen tests when enabled and when
      type legalization in LegalizeDAG is ifdef'd out.
      
      llvm-svn: 44300
      f81d5886
  11. Nov 21, 2007
  12. Nov 19, 2007
    • Chris Lattner's avatar
      ExpandUnalignedLoad doesn't handle vectors right at all apparently. · 09c0393d
      Chris Lattner authored
      Fix a couple of problems:
      1. Don't assume the VT-1 is a VT that is half the size.
      2. Treat vectors of FP in the vector path, not the FP path.
      
      This has a couple of remaining problems before it will work with
      the code in PR1811: the code below this change assumes that it can
      use extload/shift/or to construct the result, which isn't right for
      vectors.
      
      This also doesn't handle vectors of 1 or vectors that aren't pow-2.
      
      llvm-svn: 44243
      09c0393d
Loading