Hal Finkel c404e8208c Optionally enable more-aggressive FMA formation in DAGCombine ... The heuristic used by DAGCombine to form FMAs checks that the FMUL has only one use, but this is overly-conservative on some systems. Specifically, if the FMA and the FADD have the same latency (and the FMA does not compete for resources with the FMUL any more than the FADD does), there is no need for the restriction, and furthermore, forming the FMA leaving the FMUL can still allow for higher overall throughput and decreased critical-path length. Here we add a new TLI callback, enableAggressiveFMAFusion, false by default, to elide the hasOneUse check. This is enabled for PowerPC by default, as most PowerPC systems will benefit. Patch by Olivier Sallenave, thanks! git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@218120 91177308-0d34-0410-b5e6-96231b3b80d8		2014-09-19 11:42:56 +00:00
..
CostTable.h
Target.td
TargetCallingConv.h
TargetCallingConv.td
TargetFrameLowering.h
TargetInstrInfo.h	Fix a lot of confusion around inserting nops on empty functions.	2014-09-15 18:32:58 +00:00
TargetIntrinsicInfo.h
TargetItinerary.td
TargetLibraryInfo.h
TargetLowering.h	Optionally enable more-aggressive FMA formation in DAGCombine	2014-09-19 11:42:56 +00:00
TargetLoweringObjectFile.h
TargetMachine.h	Add a new pass FunctionTargetTransformInfo. This pass serves as a	2014-09-18 00:34:14 +00:00
TargetOpcodes.h
TargetOptions.h
TargetRegisterInfo.h
TargetSchedule.td
TargetSelectionDAG.td
TargetSelectionDAGInfo.h
TargetSubtargetInfo.h	Remove resetSubtargetFeatures as it is unused.	2014-09-03 20:36:31 +00:00