Andrew Trick 0c83424556 Move GenericScheduler and PostGenericScheduler into a header. ... These were not exposed previously because I didn't want out-of-tree targets to be too dependent on their internals. They can be reused for a very wide variety of processors with casual scheduling needs without exposing the classes by instead using hooks defined in MachineSchedPolicy (we can add more if needed). When targets are more aggressively tuned or want to provide custom heuristics, they can define their own MachineSchedStrategy. I tend to think this is better once you start customizing heuristics because you can copy over only what you need. I don't think that layering heuristics generally works well. However, Arch64 targets now want to reuse the Generic scheduling logic but also provide extensions. I don't see much harm in exposing the Generic scheduling classes with a major caveat: these scheduling strategies may change in the future without validating performance on less mainstream processors. If you want to be immune from changes, just define your own MachineSchedStrategy. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@210166 91177308-0d34-0410-b5e6-96231b3b80d8		2014-06-04 07:06:18 +00:00
..
llvm	Move GenericScheduler and PostGenericScheduler into a header.	2014-06-04 07:06:18 +00:00
llvm-c	[modules] Add module maps for LLVM. These are not quite ready for prime-time	2014-05-21 02:46:14 +00:00