Don't share functional units among the PPC itineraries
Instead of sharing functional unit names between the various PPC itineraries, give each core its own unit names prefixed with the core name. This follows the convention used by other backends (such as ARM), and removes a non-obvious ordering dependency between the various PPCSchedule*.td files. No functionality change intended. llvm-svn: 195908
Showing
- llvm/lib/Target/PowerPC/PPCSchedule.td 0 additions, 15 deletionsllvm/lib/Target/PowerPC/PPCSchedule.td
- llvm/lib/Target/PowerPC/PPCSchedule440.td 550 additions, 537 deletionsllvm/lib/Target/PowerPC/PPCSchedule440.td
- llvm/lib/Target/PowerPC/PPCScheduleA2.td 59 additions, 59 deletionsllvm/lib/Target/PowerPC/PPCScheduleA2.td
- llvm/lib/Target/PowerPC/PPCScheduleE500mc.td 197 additions, 172 deletionsllvm/lib/Target/PowerPC/PPCScheduleE500mc.td
- llvm/lib/Target/PowerPC/PPCScheduleE5500.td 234 additions, 205 deletionsllvm/lib/Target/PowerPC/PPCScheduleE5500.td
- llvm/lib/Target/PowerPC/PPCScheduleG3.td 61 additions, 55 deletionsllvm/lib/Target/PowerPC/PPCScheduleG3.td
- llvm/lib/Target/PowerPC/PPCScheduleG4.td 78 additions, 66 deletionsllvm/lib/Target/PowerPC/PPCScheduleG4.td
- llvm/lib/Target/PowerPC/PPCScheduleG4Plus.td 92 additions, 72 deletionsllvm/lib/Target/PowerPC/PPCScheduleG4Plus.td
- llvm/lib/Target/PowerPC/PPCScheduleG5.td 93 additions, 80 deletionsllvm/lib/Target/PowerPC/PPCScheduleG5.td
Loading
Please register or sign in to comment