forked from OSchip/llvm-project
477a1dce2b
When our RuntimeDebugBuilder calles fflush(NULL) to flush all output streams, it is important that the types we use in the call match the ones used in a declaration of fflush possible already available in the translation unit. As we just pass on a NULL pointer, the type of the pointer value does not really matter. However, as LLVM complains in case of mismatched types, we make sure to create a NULL pointer of identical type. No test case, as RuntimeDebugBuilder is not permanently used in Polly. Calls to it are until now only used to add informative output during debugging sessions. llvm-svn: 221251 |
||
|---|---|---|
| .. | ||
| autoconf | ||
| cmake | ||
| docs | ||
| include | ||
| 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.