From: Xinliang David Li <davidxl@google.com>
To: Diego Novillo <dnovillo@google.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Dump before flag
Date: Tue, 07 Jun 2011 16:51:00 -0000 [thread overview]
Message-ID: <BANLkTi=78w1_N+c-PGgV1K+m6C5+i6jJZW-pinvicXDitiq6dw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimRE8HNRZax+g6Fu714drsoUazAoA@mail.gmail.com>
Any suggestions on the dump position specification string, before and
after is not enough. How about
start, before, after, and finish?
I.e.
-fdump-tree-pre-start --> dump IR before TODO_start of PRE pass
-fdump-tree-pre-before --> dump IR just before PRE after its TODO start finishes
-fdump-tree-pre-after --> dump IR just after PRE
-fdump-tree-pre-finish --> dump it after TODO_finish of PRE?
Thanks,
David
On Tue, Jun 7, 2011 at 9:43 AM, Diego Novillo <dnovillo@google.com> wrote:
> On Tue, Jun 7, 2011 at 02:36, Richard Guenther
> <richard.guenther@gmail.com> wrote:
>
>>> For one thing, you need to either remember what is the previous pass,
>>> or dump all passes which for large files can take very long time. Even
>>> with all the dumps, you will need to eyeballing to find the previous
>>> pass which may or may not have the IR dumped.
>>>
>>> How about removing dump TODO?
>>
>> Yeah, I think this would go in the right direction.
>
> Agreed.
>
>
> Diego.
>
next prev parent reply other threads:[~2011-06-07 16:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 20:26 Xinliang David Li
2011-06-01 20:37 ` Richard Guenther
2011-06-01 20:38 ` Xinliang David Li
2011-06-01 21:12 ` Basile Starynkevitch
2011-06-01 21:24 ` Xinliang David Li
2011-06-06 11:12 ` Richard Guenther
2011-06-06 16:21 ` Xinliang David Li
2011-06-07 9:36 ` Richard Guenther
2011-06-07 16:23 ` Xinliang David Li
2011-06-07 16:43 ` Diego Novillo
2011-06-07 16:51 ` Xinliang David Li [this message]
2011-06-07 17:01 ` Diego Novillo
2011-06-07 17:07 ` Xinliang David Li
2011-06-07 17:26 ` Diego Novillo
2011-06-07 23:24 ` Xinliang David Li
2011-06-07 23:34 ` Xinliang David Li
2011-06-08 6:44 ` Xinliang David Li
2011-06-08 9:29 ` Richard Guenther
2011-06-08 16:52 ` Xinliang David Li
2011-06-08 17:14 ` Xinliang David Li
2011-06-08 23:15 ` Xinliang David Li
2011-06-09 9:28 ` Richard Guenther
2011-06-09 15:58 ` Xinliang David Li
2011-06-10 9:04 ` Richard Guenther
2011-06-10 16:54 ` Xinliang David Li
2011-06-10 18:49 ` Xinliang David Li
2011-06-14 14:19 ` Richard Guenther
2011-06-14 16:02 ` Xinliang David Li
2011-06-14 20:05 ` Xinliang David Li
2011-06-14 23:22 ` Xinliang David Li
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='BANLkTi=78w1_N+c-PGgV1K+m6C5+i6jJZW-pinvicXDitiq6dw@mail.gmail.com' \
--to=davidxl@google.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@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).