From cTuning.org
(Difference between revisions)
| Line 3: | Line 3: | ||
* ''Albert Cohen, INRIA'': I'd love to raise the issue about learning curve and development productivity with GCC code base. | * ''Albert Cohen, INRIA'': I'd love to raise the issue about learning curve and development productivity with GCC code base. | ||
| - | * ''Grigori Fursin, INRIA'': I would like to discuss further extensions to [[CTools:ICI]] needed to provide compiler/architecture/language independent API for program analysis and optimization (unified data exchange format?) that may be needed for our further research on fine-grain iterative compilation, reactive iterative compilation, collective optimization and split-compilation... | + | * ''Grigori Fursin, INRIA'': I would like to discuss further extensions to [[CTools:ICI|ICI]] and MILEPOST GCC needed to provide compiler/architecture/language independent API for program analysis and optimization (unified data exchange format?) that may be needed for our further research on fine-grain iterative compilation, reactive iterative compilation, collective optimization and split-compilation... |
Revision as of 06:27, 22 January 2010
Assorted questions for the panel:
- Albert Cohen, INRIA: I'd love to raise the issue about learning curve and development productivity with GCC code base.
- Grigori Fursin, INRIA: I would like to discuss further extensions to ICI and MILEPOST GCC needed to provide compiler/architecture/language independent API for program analysis and optimization (unified data exchange format?) that may be needed for our further research on fine-grain iterative compilation, reactive iterative compilation, collective optimization and split-compilation...