Le Mon, Nov 27, 2006 at 11:54:20AM +1100, Ben Elliston écrivait/wrote: > > I am considering implementing the following feature into GCC using > > the patch on http://gcc.gnu.org/ml/gcc-patches/2006-11/msg01769.html > > : a compiler probe which permits to probe the run of a compilation, > > e.g. by displaying in emacs or a graphical GTK application the > > current pass, Gimple representations, etc.. > > What you're describing sounds a bit like the VISTA interactive > compilation environment which allows users to dynamically adjust the > optimisation regime of individual functions and examine the effect: > > http://citeseer.ist.psu.edu/433065.html
A big thanks for your reference.; I am glancing at it. But my idea, within the GlobalGCC project http://gcc.gnu.org/ml/gcc/2006-10/msg00676.html (where we expect analysis to last dozens of minutes of compilation time on a whole program) was not to drive interactively the compilation (or the analysis), but only to show interactively the results of static analysis (and also, using the same machinery, of already existing transformations) and more genera lly some current state of the (long lasting) compilation. static analysis produce a large amount of data which could be useful to users. Nearly all the static analysers I know about have some user interface; usually by being able to show to the user the information computed for a given control point (or source location) See in particular http://www.di.ens.fr/~goubault/papers/icse01.ps.gz I see two alternatives: either plug a "compiler probe" like the one I suggested initially. alternatively, dump some of the intermediate results on the disk and have a utility to display it offline. (BTW, I could postopone the decision later) Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faïencerie, 92340 Bourg La Reine, France *** opinions {are only mines, sont seulement les miennes} ***
