From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: David Malcolm <dmalcolm@redhat.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"gcc-python-plugin@lists.fedorahosted.org"
<gcc-python-plugin@lists.fedorahosted.org>
Subject: Re: A visualization of GCC's passes, as a subway map
Date: Tue, 12 Jul 2011 15:07:00 -0000 [thread overview]
Message-ID: <4E1C4D63.3030900@oarcorp.com> (raw)
In-Reply-To: <4E1BF650.1010503@gnu.org>
On 07/12/2011 02:22 AM, Paolo Bonzini wrote:
> On 07/11/2011 07:56 PM, David Malcolm wrote:
>> Hope this is fun/helpful (and that I'm correctly interpreting the data!)
> You are, and it shows some bugs even. gimple_lcx is obviously destroyed
> by expand, and I find it unlikely that no pass ever introduces a
> critical edge...
>
David deserves a pat on the back. This is a nice way to
visualize this. It is complicated and hard to grok otherwise.
This would be a great addition to gcc internals documentation.
Especially if you could click on each pass and get to a description.
> Paolo
--
Joel Sherrill, Ph.D. Director of Research& Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next prev parent reply other threads:[~2011-07-12 13:34 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
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 [this message]
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=4E1C4D63.3030900@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=bonzini@gnu.org \
--cc=dmalcolm@redhat.com \
--cc=gcc-python-plugin@lists.fedorahosted.org \
--cc=gcc@gcc.gnu.org \
/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).