From cTuning.org
Line 33: | Line 33: | ||
{{News1| | {{News1| | ||
- | *'''2009.June.26''' - We participated in discussions to include plugin system similar to [http://ctuning.org/ici ICI] to mainline GCC for a long time and finally GCC 4.5 will feature a low-level plugin system. We are now synchronizing high-level ICI/MILEPOST with the mainline to be able to reuse all our available plugins. We also develop several new plugins within [http://socghop.appspot.com/org/home/google/gsoc2009/gcc Google Summer of Code'2009] to enable XML representation of the compilation flow, fine-grain program optimizations and instrumentation, automatic tuning of optimization heuristic based on machine learning, and function-level run-time adaptation. Comparison of GCC low-level and high-level ICI plugins is available [http://gcc.gnu.org/wiki/GCC_PluginComparison here]. The ICI development and discussions mailing list is available [http://groups.google.com/group/ctuning-discussions here]. | + | *'''2009.June.26''' - The pdf of the paper that describes Collective Tuning Infrastructure and cTuning concept (presented at the GCC Summit'09) will be available in a few weeks [http://unidapt.org/index.php/Dissemination#Fur2009 here]. |
+ | *'''2009.June.17''' - We participated in discussions to include plugin system similar to [http://ctuning.org/ici ICI] to mainline GCC for a long time and finally GCC 4.5 will feature a low-level plugin system. We are now synchronizing high-level ICI/MILEPOST with the mainline to be able to reuse all our available plugins. We also develop several new plugins within [http://socghop.appspot.com/org/home/google/gsoc2009/gcc Google Summer of Code'2009] to enable XML representation of the compilation flow, fine-grain program optimizations and instrumentation, automatic tuning of optimization heuristic based on machine learning, and function-level run-time adaptation. Comparison of GCC low-level and high-level ICI plugins is available [http://gcc.gnu.org/wiki/GCC_PluginComparison here]. The ICI development and discussions mailing list is available [http://groups.google.com/group/ctuning-discussions here]. | ||
* '''2009.June.01''' - After nearly 1 year of developments we released/updated all our open-source collaborative [[CTools|R&D tools]]: | * '''2009.June.01''' - After nearly 1 year of developments we released/updated all our open-source collaborative [[CTools|R&D tools]]: | ||
** fully redesigned and documented [[CTools:ICI|Interactive Compilation Interface]] v2.0 for GCC 4.4.0 synchronized with the official plugin GCC branch - transforming compilers into plugin-enabled research toolsets | ** fully redesigned and documented [[CTools:ICI|Interactive Compilation Interface]] v2.0 for GCC 4.4.0 synchronized with the official plugin GCC branch - transforming compilers into plugin-enabled research toolsets |
Revision as of 15:25, 26 June 2009
![]() |
Interactive Compilation Interface |
Enabling Collaborative Interactive Research Compilers |
Navigation: cTuning.org > CTools The Interactive Compilation Interface (or 'ICI' for short) is a plugin system with a high-level compiler-independent and low-level compiler-dependent API to transform current compilers into collaborative open modular interactive toolsets. The ICI framework acts as a "middleware" interface between the compiler and the user-definable plugins. It opens up and reuses the production-quality compiler infrastructure to enable program analysis and instrumentation, fine-grain program optimizations, simple prototyping of new development and research ideas while avoiding building new compilation tools from scratch. For example, it is used in MILEPOST GCC to automate compiler and architecture design and program optimizations based on statistical analysis and machine learning. It should enable universal self-tuning compilers adaptable to heterogeneous, reconfigurable, multi-core architectures ranging from supercomputers to embedded systems.
![]() ICI is an open collaborative community-driven project. You are welcome to join and participate in developments, discussions, provide feedback or suggestions to extend ICI or add new features. We develop ICI for GCC at the moment, but trying to keep it compiler independent in case someone would like to port it to other compilers to extend collaborative tools. |
|
ICI supporters: |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() You are welcome to register your interest at this page. |