public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Mingjie Xing <mingjie.xing@gmail.com>
Cc: gcc@gcc.gnu.org, gcc-python-plugin@lists.fedorahosted.org
Subject: Re: A visualization of GCC's passes, as a subway map
Date: Tue, 12 Jul 2011 16:53:00 -0000	[thread overview]
Message-ID: <1310487377.23887.35664.camel@surprise> (raw)
In-Reply-To: <CADNgcEyrR9cGEUwJ3Ui-n+Do7SnmK+Riw7+goxW08VGVA-hk8g@mail.gmail.com>

On Tue, 2011-07-12 at 11:43 +0800, Mingjie Xing wrote:
> 2011/7/12 David Malcolm <dmalcolm@redhat.com>:
> > For fun over the weekend I wrote a python script (using my
> > gcc-python-plugin[1]) to render an SVG diagram of GCC's optimization
> > passes (or, at least, based on my understanding of them).
> >
> > This diagram shows the various GCC optimization passes, arranged
> > vertically, showing child passes via indentation.
> 
> Interesting.  I also have a plugin
> (http://code.google.com/p/gcc-vcg-plugin) which can be used to dump
> the gcc pass lists in vcg format.

Thanks!  This looks useful; I'm getting rather tired of dealing with
graphviz's almost-HTML-but-not-quite format :(

FWIW, your plugin's page links to http://code.google.com/p/vcgviewer/
but that's currently giving me a 403 permissions error.  I don't know if
this is a bug at google's end or not.


Dave

  reply	other threads:[~2011-07-12 16:19 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 [this message]
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
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=1310487377.23887.35664.camel@surprise \
    --to=dmalcolm@redhat.com \
    --cc=gcc-python-plugin@lists.fedorahosted.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mingjie.xing@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).