On Tue, Jul 12, 2011 at 10:55 AM, David Malcolm <dmalc...@redhat.com> wrote: > On Tue, 2011-07-12 at 09:15 -0700, Xinliang David Li wrote: >> FYI. If you just want text dump of gcc passes and their on|off >> settings, option -fdump-passes can be used. This can be enhanced to >> dump properties and TODOs. > > Thanks! > > I got a bit mystified by: > > $ gcc -fdump-passes test.c > cc1: error: unrecognized command line option ‘-fdump-passes’ > > but it turns out I'm still stuck on 4.6.0 (though that's a restriction > I've imposed on myself), and that you added it in 4.7, if I'm reading > the history right: > http://gcc.gnu.org/viewcvs?view=revision&revision=174930 >
Right, it is in trunk compiler only. > FWIW, the analagous python code I used to generate my tables of passes > is here: > http://git.fedorahosted.org/git/?p=gcc-python-plugin.git;a=blob;f=generate-tables-of-passes-rst.py > > I don't know if it's sane in 4.6 to expose the "is_on" and > "is_really_on" booleans as (readonly) attributes of the Python gcc.Pass > objects; there seem to have been a lot of cleanups to that code in 4.7 > Other related pass related infrastructure changes include 1) -fenable-xxx=<func_ranges>, -fdisable-xxx=<func_ranges> to disable or enable any gcc passes 2) Removing IR/debug dump as a TODO. David > [snip] > > Dave > >
