From: Richard Biener <richard.guenther@gmail.com>
To: Teresa Johnson <tejohnson@google.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
David Li <davidxl@google.com>
Subject: Re: [PATCH] Add missing -fdump-* options
Date: Tue, 13 May 2014 08:39:00 -0000 [thread overview]
Message-ID: <CAFiYyc3-LkfbwOX2bjhPDR0o8+PowRBbCTWd+b20-8J+-KdE_w@mail.gmail.com> (raw)
In-Reply-To: <CAAe5K+XJ4_Cj3uH3pguJ33H33T2XtKKETf0Jm81L9141d5Bm2w@mail.gmail.com>
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?
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
next prev parent reply other threads:[~2014-05-13 8:39 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 [this message]
2014-05-13 13:18 ` Teresa Johnson
2014-05-13 15:19 ` Xinliang David Li
2014-06-25 14:22 ` Teresa Johnson
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=CAFiYyc3-LkfbwOX2bjhPDR0o8+PowRBbCTWd+b20-8J+-KdE_w@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tejohnson@google.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).