Michael Kruse d632378f2f [LoopUnroll] Honor '#pragma unroll' even with -fno-unroll-loops. ... When using clang with `-fno-unroll-loops` (implicitly added with `-O1`), the LoopUnrollPass is not not added to the (legacy) pass pipeline. This also means that it will not process any loop metadata such as llvm.loop.unroll.enable (which is generated by #pragma unroll or WarnMissedTransformationsPass emits a warning that a forced transformation has not been applied (see https://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20181210/610833.html). Such explicit transformations should take precedence over disabling heuristics. This patch unconditionally adds LoopUnrollPass to the optimizing pipeline (that is, it is still not added with `-O0`), but passes a flag indicating whether automatic unrolling is dis-/enabled. This is the same approach as LoopVectorize uses. The new pass manager's pipeline builder has no option to disable unrolling, hence the problem does not apply. Differential Revision: https://reviews.llvm.org/D55716 llvm-svn: 349509		2018-12-18 17:16:05 +00:00
..
llvm	[LoopUnroll] Honor '#pragma unroll' even with -fno-unroll-loops.	2018-12-18 17:16:05 +00:00
llvm-c	[IR] Add a dedicated FNeg IR Instruction	2018-11-13 18:15:47 +00:00