From: Xinliang David Li <davidxl@google.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Diego Novillo <dnovillo@google.com>
Subject: Re: Dump before flag
Date: Tue, 07 Jun 2011 16:23:00 -0000 [thread overview]
Message-ID: <BANLkTiktb0zbKcaDwTU4OLdwtU5uOLmup-VaPrbBX6u0yHKwKQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin6DK8LZEq-TbjrqWKD1oJXJG1xeA@mail.gmail.com>
On Tue, Jun 7, 2011 at 2:36 AM, Richard Guenther
<richard.guenther@gmail.com> wrote:
> On Mon, Jun 6, 2011 at 6:20 PM, Xinliang David Li <davidxl@google.com> wrote:
>>>
>>> Your patch doesn't really improve this but adds to the confusion.
>>>
>>> + /* Override dump TODOs. */
>>> + if (dump_file && (pass->todo_flags_finish & TODO_dump_func)
>>> + && (dump_flags & TDF_BEFORE))
>>> + {
>>> + pass->todo_flags_finish &= ~TODO_dump_func;
>>> + pass->todo_flags_start |= TODO_dump_func;
>>> + }
>>>
>>> and certainly writing to pass is not ok. And the TDF_BEFORE flag
>>> looks misplaced as it controls TODOs, not dumping behavior.
>>> Yes, it's a mess right now but the above looks like a hack ontop
>>> of that mess (maybe because of it, but well ...).
>>>
>>
>> How about removing dumping TODO completely -- this can be done easily
>> -- I don't understand why pass wants extra control on the dumping if
>> user already asked for dumping -- it is annoying to see empty IR dump
>> for a pass when I want to see it.
>>
>>> At least I would have expected to also get the dump after the
>>> pass, not only the one before it with this dump flag.
>>>
>>> Now, why can't you look at the previous pass output for the
>>> before-dump (as I do usually)?
>>
>> 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. Currently some passes
> do not dump function bodies because they presumably do no IL
> modification. But this is certainly the minority (and some passes do not
> dump bodies even though they are modifying the IL ...).
>
> So I'd say we should by default dump function bodies.
>
> Note that there are three useful dumping positions (maybe four),
> before todo-start, after todo-start, before todo-finish and after todo-finish.
> By default we'd want after todo-finish. When we no longer dump via
> a TODO then we could indeed use dump-flags to control this
> (maybe -original for the body before todo-start).
>
> What to others think?
I think that is a very good thing to have.
David
>
> Richard.
>
>> Thanks,
>>
>> David
>>
>>
>>>
>>> Richard.
>>>
>>
>
next prev parent reply other threads:[~2011-06-07 16:23 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 [this message]
2011-06-07 16:43 ` Diego Novillo
2011-06-07 16:51 ` Xinliang David Li
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=BANLkTiktb0zbKcaDwTU4OLdwtU5uOLmup-VaPrbBX6u0yHKwKQ@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).