Arnold Schwaighofer d42730dc71 IfConverter: Use TargetSchedule for instruction latencies ... For targets that have instruction itineraries this means no change. Targets that move over to the new schedule model will use be able the new schedule module for instruction latencies in the if-converter (the logic is such that if there is no itineary we will use the new sched model for the latencies). Before, we queried "TTI->getInstructionLatency()" for the instruction latency and the extra prediction cost. Now, we query the TargetSchedule abstraction for the instruction latency and TargetInstrInfo for the extra predictation cost. The TargetSchedule abstraction will internally call "TTI->getInstructionLatency" if an itinerary exists, otherwise it will use the new schedule model. ATTENTION: Out of tree targets! (I will also send out an email later to LLVMDev) This means, if your target implements unsigned getInstrLatency(const InstrItineraryData *ItinData, const MachineInstr *MI, unsigned *PredCost); and returns a value for "PredCost", you now also need to implement unsigned getPredictationCost(const MachineInstr *MI); (if your target uses the IfConversion.cpp pass) radar://15077010 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@191671 91177308-0d34-0410-b5e6-96231b3b80d8		2013-09-30 15:28:56 +00:00
..
CostTable.h
Mangler.h
Target.td
TargetCallingConv.h
TargetCallingConv.td
TargetFrameLowering.h
TargetInstrInfo.h	IfConverter: Use TargetSchedule for instruction latencies	2013-09-30 15:28:56 +00:00
TargetIntrinsicInfo.h
TargetItinerary.td
TargetJITInfo.h
TargetLibraryInfo.h
TargetLowering.h
TargetLoweringObjectFile.h
TargetMachine.h
TargetOpcodes.h
TargetOptions.h
TargetRegisterInfo.h
TargetSchedule.td
TargetSelectionDAG.td
TargetSelectionDAGInfo.h
TargetSubtargetInfo.h