Michael Kruse 58fa3bb63a Do not store scalar accesses in InstructionToAccess ... At code generation, scalar reads are generated before the other statement's instructions, respectively scalar writes after them, in contrast to array accesses which are "executed" with the instructions they are linked to. Therefore it makes sense to not map the scalar accesses to a place of execution. Follow-up patches will also remove some of the directs links from a scalar access to a single instruction, such that only having array accesses in InstructionToAccess ensures consistency. Differential Revision: http://reviews.llvm.org/D13676 llvm-svn: 256298		2015-12-22 23:25:11 +00:00
..
Analysis	Do not store scalar accesses in InstructionToAccess	2015-12-22 23:25:11 +00:00
CodeGen	Refactor canSynthesize in the BlockGenerators [NFC]	2015-12-22 19:08:49 +00:00
Exchange	Adjust formatting to clang-format changes in 256149	2015-12-21 12:38:56 +00:00
External	Update isl to isl-0.15-142-gf101714	2015-12-04 08:46:14 +00:00
JSON	Added arcanist linters and cleaned errors and warnings	2014-08-18 00:40:13 +00:00
Support	Print "null" for ISL objects that are nullptr	2015-12-13 19:35:26 +00:00
Transform	Adjust formatting to clang-format changes in 256149	2015-12-21 12:38:56 +00:00
CMakeLists.txt	IR cleanup after CodeGeneration	2015-11-26 12:36:25 +00:00
Makefile	Remove independent blocks pass	2015-10-18 12:28:00 +00:00
Polly.cpp	…