From: Aditya K <hiraditya@msn.com>
To: Jeff Law <law@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] Print Pass Names
Date: Tue, 26 May 2015 14:51:00 -0000 [thread overview]
Message-ID: <BLU179-W94C7A30C16C693973D1497B6CC0@phx.gbl> (raw)
In-Reply-To: <555F970D.30207@redhat.com>
I don't have commit access. I would appreciate if someone does that for me.
Thanks,
-Aditya
----------------------------------------
> Date: Fri, 22 May 2015 14:52:29 -0600
> From: law@redhat.com
> To: hiraditya@msn.com; richard.guenther@gmail.com; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] Print Pass Names
>
> On 05/22/2015 02:38 PM, Aditya K wrote:
>>
>>
>> ----------------------------------------
>>> Subject: Re: [PATCH] Print Pass Names
>>> From: richard.guenther@gmail.com
>>> Date: Fri, 22 May 2015 21:32:24 +0200
>>> To: hiraditya@msn.com; gcc-patches@gcc.gnu.org
>>>
>>> On May 22, 2015 6:32:38 PM GMT+02:00, Aditya K <hiraditya@msn.com> wrote:
>>>> Currently, when we print the passes it does not print its name. This
>>>> becomes confusing when we want to print all the passes at once (e.g.,
>>>> -fdump-tree-all-all=stderr &> pass.dump).
>>>> This patch adds functionality to print the pass name. It passes
>>>> bootstrap (with default configurations).
>>>>
>>>> Hope this is useful.
>>>
>>> Can't you just use current_pass->name?
>>
>> You are right. I have updated the patch.
>> Thanks
>> -Aditya
>>
>> gcc/ChangeLog:
>>
>> 2015-05-22 Aditya Kumar <hiraditya@msn.com>
>>
>> * statistics.c (statistics_fini_pass): Print pass name.OK.
> jeff
>
next prev parent reply other threads:[~2015-05-26 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 17:04 Aditya K
2015-05-22 19:59 ` Richard Biener
2015-05-22 20:55 ` Aditya K
2015-05-22 21:09 ` Jeff Law
2015-05-26 14:51 ` Aditya K [this message]
2015-05-27 15:25 ` Jeff Law
2015-05-27 19:58 ` Aditya K
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=BLU179-W94C7A30C16C693973D1497B6CC0@phx.gbl \
--to=hiraditya@msn.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--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).