b39c96aa19
In case the original parameter instruction does not have a name, but it comes from a load instruction where the base pointer has a name we used the name of the load instruction to give some more intuition of where the parameter came from. To ensure this works also through GEPs which may have complex offsets, we originally just dropped the offsets and _only_ used the base pointer name. As this can result in multiple parameters to get the same name, we now prefix the parameter ID to ensure parameter names are unique. This will make it easier to understand debug output. This change does not affect correctness, as parameter IDs (even of the same name) can always be distinguished through the SCEV pointer stored inside them. llvm-svn: 253330 |
||
|---|---|---|
| .. | ||
| autoconf | ||
| cmake | ||
| include/polly | ||
| lib | ||
| test | ||
| tools | ||
| utils | ||
| www | ||
| .arcconfig | ||
| .arclint | ||
| .gitattributes | ||
| .gitignore | ||
| CMakeLists.txt | ||
| CREDITS.txt | ||
| LICENSE.txt | ||
| Makefile | ||
| Makefile.common.in | ||
| Makefile.config.in | ||
| README | ||
| configure | ||
README
Polly - Polyhedral optimizations for LLVM ----------------------------------------- http://polly.llvm.org/ Polly uses a mathematical representation, the polyhedral model, to represent and transform loops and other control flow structures. Using an abstract representation it is possible to reason about transformations in a more general way and to use highly optimized linear programming libraries to figure out the optimal loop structure. These transformations can be used to do constant propagation through arrays, remove dead loop iterations, optimize loops for cache locality, optimize arrays, apply advanced automatic parallelization, drive vectorization, or they can be used to do software pipelining.