Hideki Saito 6adf799873 [NFC][LV][LoopUtil] Move LoopVectorizationLegality to its own file ... Summary: This is a follow up to D45420 (included here since it is still under review and this change is dependent on that) and D45072 (committed). Actual change for this patch is LoopVectorize* and cmakefile. All others are all from D45420. LoopVectorizationLegality is an analysis and thus really belongs to Analysis tree. It is modular enough and it is reusable enough ---- we can further improve those aspects once uses outside of LV picks up. Hopefully, this will make it easier for people familiar with vectorization theory, but not necessarily LV itself to contribute, by lowering the volume of code they should deal with. We probably should start adding some code in LV to check its own capability (i.e., vectorization is legal but LV is not ready to handle it) and then bail out. Reviewers: rengolin, fhahn, hfinkel, mkuper, aemerson, mssimpso, dcaballe, sguggill Reviewed By: rengolin, dcaballe Subscribers: egarcia, rogfer01, mgorny, llvm-commits Differential Revision: https://reviews.llvm.org/D45552 llvm-svn: 331139		2018-04-29 07:26:18 +00:00
..
llvm	[NFC][LV][LoopUtil] Move LoopVectorizationLegality to its own file	2018-04-29 07:26:18 +00:00
llvm-c	[LLVM-C] Add DIBuilder bindings to create import declarations	2018-04-28 22:32:07 +00:00