Hi Basile et al, > My suggestion to ICI friends is : just propose quickly your needed plugin > events, and make > your ICI a GPLv3 plugin. > When you can show that your ICI plugin to an *unmodified* gcc-4.5 brings some > value, GCC > people will perhaps start to > listen and look inside.
Just to mention that I am a bit confused because I actually don't expect to have problems moving ICI to the mainline unless we find some big bugs that can change GCC behavior (but I really don't think so). We had many online and offline discussions to move ICI to the mainline GCC in the last few years with GCC colleagues/maintainers. We just sadly got delayed at INRIA this summer due to different reasons but Joern is now working with us for 2 months fully time to clean and test ICI and submit patches as soon as they are ready. It's true that we actually need a few hooks and Joern will communicate about that shortly BUT these hooks are already used in real plugins for real performance tuning (in a way as current hooks are used in Dehydra for real program analysis in several companies). Our performance results are gradually added to the online performance database at http://cTuning.org/cdatabase for EEMBC, SPEC and other programs across multiple architectures which real users and companies are using to optimize their real code... A few days ago I got a feedback from Loongson group that they considerably speeded up EEMBC on their latest processor using GCC 4.4.x and they should upload the results to the database shortly ... They have been actively working with us using and extending ICI ... That's why only after we showed real results, we would now like to have MINIMAL ICI in mainline GCC but patches for other extensions including GSOC'09 projects will be submitted to GCC only after testing ... We will keep in touch about that, Grigori
