This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Sequence of access to passes.c
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andi Hellmund wrote:
> Ian Lance Taylor wrote:
>> Ankit Mahanot <ankit1986@gmail.com> 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
>>
>>
Personally i prefer ack-grep http://betterthangrep.com/ :) its a nicer
grep though i am sure you can use grep to do the same as this as it is
just a wrapper over grep i think :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkqpX+UACgkQAhcOgIaQQ2G31ACbBlJ0rpGQfilA5pv3MN6N0jv5
YUkAmgIu9obLhsMj3RUmzN617D4/4CpW
=bgGj
-----END PGP SIGNATURE-----