Description of the Project:
While the standard Polly-enabled -O1/-O2/-O3 optimization pass pipelines work fine with the New Pass Manager (NPM), some parts of Polly still only works with the legacy pass manager. This includes some passes such as -polly-export-jscop/-polly-export-jscop, regression testing, Polly-ACC, command line options such as -polly-show, the PassInstrumentation mechanism used by e.g. -print-after-all. LLVM (and Clang) have moved to NPM being the default and support for the legacy pass manager is deprecated, slowly degenerates and features getting removed.
That is, all of Polly’s functionality should eventually work with the NPM as well, and be prepared for the complete removal of the legacy pass manager. More details about the two pass managers found here.
Expected results:
The goal is to make Polly more usable with using only the NPM. Milestones, not necessarily all to be reached in this GSoC, are:
- Make all of Polly’s functionality available in the NPM (or decide to deprecate/remove it)
- Better integration into the NPM (such as supporting PassInstrumentation); If the NPM turns out to be inadequate, use only a monolothic function pass.
- Replace the legacy pass manager in regression tests.
- Be ready for complete removal of the legacy pass manager in LLVM.
Confirmed mentors: @Meinersbur
Desirable skills: Understanding of the C++ template pattern used by the new pass manager (CRTP, Mixins, etc). Familarity with how LLVM can be linked (static, BUILD_SHARED_LIBS, and SHLIB/DYLIB) and its plugin loading machanisms (static, -load and -load-pass-plugin). Ideally, already worked with LLVM’s new pass manager.
Project size: Medium
Difficulty: Medium/Hard
. There are others who deserve this chance). If nobody submits for this project, I’d like to continue on this as a start of my exploration of polyhedral compilation.