From cTuning.org

(Difference between revisions)
Jump to: navigation, search
Line 12: Line 12:
** [[CTools:ICI:Projects:Cloning|Development page for function cloning from GSOC'09]]
** [[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]
*** [http://ctuning.org/wiki/index.php/CTools:ICI:Projects:GSOC09:Function_cloning_and_program_instrumentation documentation]
 +
** '''''We are looking for volonteers to finish the above developments inside GCC 4.5.x/4.6'''''
* '''Grigori:''' - we should one day add caching of best optimization flags locally not to connect to cTuning web-services all the time...
* '''Grigori:''' - we should one day add caching of best optimization flags locally not to connect to cTuning web-services all the time...

Revision as of 21:54, 21 May 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 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.
  • Grigori: - we can provide similar wrappers as from MILEPOST GCC to other compilers while using MILEPOST GCC for feature extraction. DONE. See cTuning CC

Locations of visitors to this page