Ian Lance Taylor wrote: > Ankit Mahanot <ankit1986@xxxxxxxxx> writes: > > >> 1) passes.c calls all the optimizations. But how does the control >> reach passes.c. I mean when a code starts compiling, which file calls >> passes.c >> > > grep is your friend. Look for the various calls to execute_pass_list. > If grep is too cumbersome for you :), I would recommend the use of cscope which allows you to browse the source code for e.g. function defintions and function references. This is probably more programming-oriented than grep. Take a lot at: * **http://cscope.sourceforge.net/* and at * **cscope.sourceforge.net/cscope_vim_tutorial.html* for the integration of cscope into vim Andi > >> 2) Where should I write my code. In passes.c OR somewhere else ?? >> > > If you want to change the order of passes, then passes.c seems like a > good place. Note that mainline gcc has support for plugins to add new > passes which you might want to look at. > > >> 3) is online profiling possible because i want to calculate the time >> taken by different optimizations & apply the algo based on those >> timings. >> > > See -ftime-report. > > Ian > >
