public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Teresa Johnson <tejohnson@google.com>
To: Xinliang David Li <davidxl@google.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
		"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add missing -fdump-* options
Date: Wed, 25 Jun 2014 14:22:00 -0000	[thread overview]
Message-ID: <CAAe5K+XYTHxVu+gi1WM54ixf+m=EufUoNjAt-Cy5wNTS-gVEyA@mail.gmail.com> (raw)
In-Reply-To: <CAAkRFZ+wguXyxQOJMq1fiZ_YejyB8gdps6vraiAC6YuA_ixm8A@mail.gmail.com>

On Tue, May 13, 2014 at 8:19 AM, Xinliang David Li <davidxl@google.com> wrote:
> On Tue, May 13, 2014 at 1:39 AM, Richard Biener
> <richard.guenther@gmail.com> wrote:
>> On Fri, May 9, 2014 at 5:54 PM, Teresa Johnson <tejohnson@google.com> wrote:
>>> I discovered that the support for the documented -fdump-* options
>>> "optimized", "missed", "note" and "optall" was missing. Added that and
>>> fixed a minor typo in the documentation.
>>>
>>> Bootstrapped and tested on x86-64-unknown-linux-gnu. Ok for trunk?
>>
>> I'm not sure they were intented for user-consumption.  ISTR they
>> are just an implementation detail exposed by -fopt-info-X (which is
>> where they are documented).
>>
>> The typo fix is ok, also adding a comment before the dump flags
>> definition to the above fact.
>>
>> David, do I remember correctly?
>
> I remember we talked about content filtering dump flags. Things like
>
> -fdump-xxx-ir  <-- dump IR only
> -fdump-xxx-transformation <-- optimization note
> -fdump-xxx-debug <-- other debug traces
>
> Other than that, now I think 'details' and 'all' seem redundant.
> 'verbose' flag/modifier can achieve the same effect depending on the
> context.
>
> -fdump-xxx-ir-verbose <-- dump IR, and turn on IR modifiers such as
> vops, lineno, etc
> -fdump-xxx-transforamtion-verbose <-- dump transformations + missed
> optimizations + notes
> -fdump-xxx-debug-verbose <-- turn on detailed trace.

The above proposal seems fine to me as a longer-term direction, but
also seems somewhat orthogonal to the issue my patch is trying to
solve in the short term, namely inconsistent documentation and
behavior:

1) "optimized", "missed", "note" and "optall" are documented as being
sub-options for -fdump-tree-* in doc/invoke.texi, but not implemented.
2) "optimized", "missed", "note" and "optall" are however enabled via
-fdump-tree-all

Could we at least fix these issues in the short term, as it doesn't
affect the documented behavior (but rather adds the documented
behavior)?

Thanks,
Teresa

>
> thanks,
>
> David
>
>
>>
>> Thanks,
>> Richard.
>>
>>> Thanks,
>>> Teresa
>>>
>>> 2014-05-09  Teresa Johnson  <tejohnson@google.com>
>>>
>>>         * doc/invoke.texi: Fix typo.
>>>         * dumpfile.c: Add support for documented -fdump-* options
>>>         optimized/missed/note/optall.
>>>
>>> Index: doc/invoke.texi
>>> ===================================================================
>>> --- doc/invoke.texi     (revision 210157)
>>> +++ doc/invoke.texi     (working copy)
>>> @@ -6278,7 +6278,7 @@ passes).
>>>  @item missed
>>>  Enable showing missed optimization information (only available in certain
>>>  passes).
>>> -@item notes
>>> +@item note
>>>  Enable other detailed optimization information (only available in
>>>  certain passes).
>>>  @item =@var{filename}
>>> Index: dumpfile.c
>>> ===================================================================
>>> --- dumpfile.c  (revision 210157)
>>> +++ dumpfile.c  (working copy)
>>> @@ -107,6 +107,10 @@ static const struct dump_option_value_info dump_op
>>>    {"nouid", TDF_NOUID},
>>>    {"enumerate_locals", TDF_ENUMERATE_LOCALS},
>>>    {"scev", TDF_SCEV},
>>> +  {"optimized", MSG_OPTIMIZED_LOCATIONS},
>>> +  {"missed", MSG_MISSED_OPTIMIZATION},
>>> +  {"note", MSG_NOTE},
>>> +  {"optall", MSG_ALL},
>>>    {"all", ~(TDF_RAW | TDF_SLIM | TDF_LINENO | TDF_TREE | TDF_RTL | TDF_IPA
>>>             | TDF_STMTADDR | TDF_GRAPH | TDF_DIAGNOSTIC | TDF_VERBOSE
>>>             | TDF_RHS_ONLY | TDF_NOUID | TDF_ENUMERATE_LOCALS | TDF_SCEV)},
>>>
>>>
>>> --
>>> Teresa Johnson | Software Engineer | tejohnson@google.com | 408-460-2413



-- 
Teresa Johnson | Software Engineer | tejohnson@google.com | 408-460-2413

  reply	other threads:[~2014-06-25 14:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 15:54 Teresa Johnson
2014-05-13  8:39 ` Richard Biener
2014-05-13 13:18   ` Teresa Johnson
2014-05-13 15:19   ` Xinliang David Li
2014-06-25 14:22     ` Teresa Johnson [this message]
2014-06-26  7:40       ` Richard Biener
2014-06-26 17:46         ` Teresa Johnson

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='CAAe5K+XYTHxVu+gi1WM54ixf+m=EufUoNjAt-Cy5wNTS-gVEyA@mail.gmail.com' \
    --to=tejohnson@google.com \
    --cc=davidxl@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).