Supported by Polly Labs, Polly has matured over the last year. Our core math library has transitioned to a new C++ interface, the last fundamental correctness issues have been resolved, we scaled Polly to compile COSMO, the Swiss weather model covering over 16.000 loops, and extensive correctness testing has been performed by compiling the full Android Open Source Project, the 500,000 lines COSMO project, as well the gentoo package repository. New techniques to remove scalar dependences allowed us to move Polly late into the pass pipeline and now optimize C++ code as if it would be C code. We started to use hardware information to tune our performance model and even implemented support for the new pass manager. Many things changed over the last year and a growing number of developers and companies continue to actively work on Polly and related technologies.
For a lively community working worldwide, meeting and discussing in person is essential to coordinate development efforts. Many of the ideas implemented over the last year were inspired by discussions at the 2016 Polly BoF. For 2017, we expect a variety of new important topics to discuss:
- Share experience of production use and large-scale research use of Polly - How to tighten the integration of Polly within the LLVM community - High-level Loop Optimizations on C++ code: where are we, where do we want to go? - Accelerator Compilation: Polly to optimize GPGPU and FPGA code - Using ILP solvers in LLVM. Can other areas benefit? Which features can they enable? Does it make sense to use Polly’s isl solver, can we improve it, or develop an even better solver?
