Skip to content
  1. Mar 14, 2012
    • Andrew Trick's avatar
      misched: implemented a framework for top-down or bottom-up scheduling. · 8823decd
      Andrew Trick authored
      New flags: -misched-topdown, -misched-bottomup. They can be used with
      the default scheduler or with -misched=shuffle. Without either
      topdown/bottomup flag -misched=shuffle now alternates scheduling
      direction.
      
      LiveIntervals update is unimplemented with bottom-up scheduling, so
      only -misched-topdown currently works.
      
      Capped the ScheduleDAG hierarchy with a concrete ScheduleDAGMI class.
      ScheduleDAGMI is aware of the top and bottom of the unscheduled zone
      within the current region. Scheduling policy can be plugged into
      the ScheduleDAGMI driver by implementing MachineSchedStrategy.
      ConvergingScheduler is now the default scheduling algorithm.
      It exercises the new driver but still does no reordering.
      
      llvm-svn: 152700
      8823decd
    • Andrew Trick's avatar
      misched comments · 72515bef
      Andrew Trick authored
      llvm-svn: 152699
      72515bef
    • Eric Christopher's avatar
      Remove the DW_AT_MIPS_linkage name attribute when we don't need it · a9916d02
      Eric Christopher authored
      output (we're emitting a specification already and the information
      isn't changing).
      
      Saves 1% on the debug information for a build of llvm.
      
      Fixes rdar://11043421
      
      llvm-svn: 152697
      a9916d02
  2. Mar 13, 2012
  3. Mar 12, 2012
  4. Mar 11, 2012
  5. Mar 10, 2012
  6. Mar 09, 2012
  7. Mar 08, 2012
  8. Mar 07, 2012
    • Chandler Carruth's avatar
      Try to clarify this comment some. · 636ee38a
      Chandler Carruth authored
      llvm-svn: 152221
      636ee38a
    • Chandler Carruth's avatar
      Remove another outbreak of customized (and completely broken) hashing. · 962152ca
      Chandler Carruth authored
      This one is particularly annoying because the hashing algorithm is
      highly specialized, with a strange "equivalence" definition that subsets
      the fields involved.
      
      Still, this looks at the exact same set of data as the old code, but
      without bitwise or-ing over parts of it and other mixing badness. No
      functionality changed here. I've left a substantial fixme about the fact
      that there is a cleaner and more principled way to do this, but it
      requires making the equality definition actual stable for particular
      types...
      
      llvm-svn: 152218
      962152ca
Loading