From cTuning.org
Merging/testing 2009 developments to ICI 2.5
Contents |
Description
- lICI - low-level API that directly access native plugin system in GCC. Whenever we need some low-level events or changes in the compiler, we first update lICI and then gradually try to move them to the mainline
- hICI - high-level API that communicates with lAPI and normally should not require many changes in GCC but more research oriented (iterative compilation, pass reordering, machine learning)
NEEDED functionality
- function cloning - high-priority
- cleaning up control (loading plugins, pass selection on IPA and function level) - high-priority
- fine-grain optimizations
URGENT TODOs
- how to proceed with SVN, branching, etc
- Grigori suggests to use UVSQ SVN now - we need to install it ASAP ...
GCC versions support
- GCC 4.4: lICI should duplicate plugin system (since there is no one)
- GCC 4.5: lICI calls most of the native plugin functions with some new functionality
hICI is a plugin itslef as Joern already did that is communicating with our compiler-independent plugins (which is not really fully true at the moment but we will work on that)
Current functions:
GCC 4.4
lICI:
GCC 4.5
lICI: