llvm-project/polly/test
Tobias Grosser 808cd69a92 Use schedule trees to represent execution order of statements
Instead of flat schedules, we now use so-called schedule trees to represent the
execution order of the statements in a SCoP. Schedule trees make it a lot easier
to analyze, understand and modify properties of a schedule, as specific nodes
in the tree can be choosen and possibly replaced.

This patch does not yet fully move our DependenceInfo pass to schedule trees,
as some additional performance analysis is needed here. (In general schedule
trees should be faster in compile-time, as the more structured representation
is generally easier to analyze and work with). We also can not yet perform the
reduction analysis on schedule trees.

For more information regarding schedule trees, please see Section 6 of
https://lirias.kuleuven.be/handle/123456789/497238

llvm-svn: 242130
2015-07-14 09:33:13 +00:00
..
DeadCodeElimination Use schedule trees to represent execution order of statements 2015-07-14 09:33:13 +00:00
DependenceInfo Use schedule trees to represent execution order of statements 2015-07-14 09:33:13 +00:00
IndependentBlocks Remove code for scalar and PHI to array translation 2015-06-26 07:31:18 +00:00
Isl Use schedule trees to represent execution order of statements 2015-07-14 09:33:13 +00:00
ScheduleOptimizer Use schedule trees to represent execution order of statements 2015-07-14 09:33:13 +00:00
ScopDetect Remove code for scalar and PHI to array translation 2015-06-26 07:31:18 +00:00
ScopDetectionDiagnostics Update polly for LLVM rename of debug info metadata with DI* prefix 2015-04-29 17:02:14 +00:00
ScopInfo Use schedule trees to represent execution order of statements 2015-07-14 09:33:13 +00:00
TempScop Remove code for scalar and PHI to array translation 2015-06-26 07:31:18 +00:00
CMakeLists.txt Drop some CLooG leftovers 2015-03-30 17:56:50 +00:00
Makefile Drop Cloog support 2014-12-02 19:26:58 +00:00
README
create_ll.sh Small change to create_ll.sh [NFC] 2015-03-08 15:36:27 +00:00
lit.cfg Do not run GPGPU test cases without nvptx target 2014-05-14 14:18:14 +00:00
lit.site.cfg.in [tests] Use -polly-vectorizer=polly directly 2015-04-05 06:53:11 +00:00
polly.ll Remove target triples from test cases 2015-04-21 14:28:02 +00:00

README

place tests here