From cTuning.org
(Difference between revisions)
| Line 6: | Line 6: | ||
---- | ---- | ||
| + | |||
| + | * [http://socghop.appspot.com/org/home/google/gsoc2009/gcc '''Google Summer of Code'09 MILEPOST GCC extensions and plugins''' (XML representation of the compilation flow, fine-grain optimizations and instrumentation, polyhedral transformations, run-time adaptation)] | ||
| + | ** [[CTools:ICI:Projects:Fine_Grain_Optimizations|Development page for fine-grain tuning from GSOC'09]] | ||
| + | *** [http://ctuning.org/wiki/index.php/CTools:ICI:Projects:GSOC09:Fine_grain_tuning documentation] | ||
| + | ** [[CTools:ICI:Projects:Cloning|Development page for function cloning from GSOC'09]] | ||
| + | *** [http://ctuning.org/wiki/index.php/CTools:ICI:Projects:GSOC09:Function_cloning_and_program_instrumentation documentation] | ||
* '''Grigori:''' - we should one day add caching of best optimization flags locally not to connect to | * '''Grigori:''' - we should one day add caching of best optimization flags locally not to connect to | ||
Revision as of 20:15, 21 February 2010
Navigation: cTuning.org > CTools > MilepostGCC
You can provide your feedback and suggestions here or participate in the discussions. You can also contact cTuning steering committee if you have general questions. Finally, you can also select a Wiki option to watch the modifications of this page.
(simply self-register at this website to join our community and edit open Wiki pages)
- Grigori: - we should one day add caching of best optimization flags locally not to connect to
ctuning web-services all the time...
- Grigori: - we can provide similar wrappers as from MILEPOST GCC to other compilers while using
MILEPOST GCC for feature extraction...
- Grigori: - we need to do more analysis of static program features since they may not be enough
to compare programs. we should later enable finest-grain tuning of optimizations and machine learning.