From: Xinliang David Li <davidxl@google.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: "Paulo J. Matos" <pocmatos@gmail.com>, gcc@gcc.gnu.org
Subject: Re: A visualization of GCC's passes, as a subway map
Date: Tue, 12 Jul 2011 18:10:00 -0000 [thread overview]
Message-ID: <CAAkRFZLrKUheswgy9h_+VyYcVVx_h7nX0s6Ea3kqiR1aw4PNCw@mail.gmail.com> (raw)
In-Reply-To: <1310493331.23887.35775.camel@surprise>
On Tue, Jul 12, 2011 at 10:55 AM, David Malcolm <dmalcolm@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
>
>
next prev parent reply other threads:[~2011-07-12 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 17:59 David Malcolm
2011-07-12 3:43 ` Mingjie Xing
2011-07-12 16:53 ` David Malcolm
2011-07-12 7:23 ` Paolo Bonzini
2011-07-12 10:51 ` Paulo J. Matos
2011-07-12 16:08 ` Paolo Bonzini
2011-07-12 16:11 ` Paulo J. Matos
2011-07-12 16:16 ` David Malcolm
2011-07-12 16:19 ` Xinliang David Li
2011-07-12 18:08 ` David Malcolm
2011-07-12 18:10 ` Xinliang David Li [this message]
2011-07-13 9:53 ` Paolo Bonzini
2011-07-13 10:58 ` Richard Guenther
2011-07-13 13:22 ` Paolo Bonzini
2011-07-14 9:21 ` Richard Guenther
2011-07-14 10:29 ` Paolo Bonzini
2011-07-14 15:31 ` Michael Matz
2011-07-12 15:07 ` Joel Sherrill
2011-07-12 18:29 ` David Malcolm
2011-07-12 21:59 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAkRFZLrKUheswgy9h_+VyYcVVx_h7nX0s6Ea3kqiR1aw4PNCw@mail.gmail.com \
--to=davidxl@google.com \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pocmatos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).