From: Jason Merrill <jason@redhat.com>
To: Lawrence Crowl <crowl@google.com>
Cc: reply@codereview.appspotmail.com, dnovillo@google.com,
gcc-patches@gcc.gnu.org
Subject: Re: [patch] Split Parse Timevar (issue4378056)
Date: Wed, 20 Apr 2011 23:33:00 -0000 [thread overview]
Message-ID: <4DAF5782.90009@redhat.com> (raw)
In-Reply-To: <20110412184923.33F942225D6@jade.mtv.corp.google.com>
On 04/12/2011 11:49 AM, Lawrence Crowl wrote:
> This patch is available for review at http://codereview.appspot.com/4378056
I tried to comment there, but it didn't seem to be working; looking at
the side-by-side diffs didn't show any changes, and double-clicking on a
line in the patch form didn't let me add a comment.
> + timevar_start (TV_RESOLVE_OVERLOAD);
Putting this in perform_overload_resolution isn't enough; only a couple
of cases of overload resolution actually use it. Any function that
calls tourney will also need this.
> +lookup_template_class (tree d1, tree arglist, tree in_decl, tree context,
> + int entering_scope, tsubst_flags_t complain)
> +{
> + tree ret;
> + bool subtime = timevar_cond_start (TV_NAME_LOOKUP);
Let's count this as TV_INSTANTIATE_TEMPLATE instead.
> @@ -17194,7 +17225,7 @@ instantiate_decl (tree d, int defer_ok,
> - timevar_push (TV_PARSE);
> + timevar_push (TV_PARSE_GLOBAL);
This too.
> @@ -1911,7 +1911,7 @@ ggc_collect (void)
> - timevar_push (TV_GC);
> + timevar_start (TV_GC);
Why this change? GC time shouldn't be counted against whatever we
happen to be parsing when it happens.
> +DEFTIMEVAR (TV_PHASE_C_WRAPUP_CHECK , "phase C wrapup & check")
> +DEFTIMEVAR (TV_PHASE_CP_DEFERRED , "phase C++ deferred")
Why do these need to be different timevars?
> +DEFTIMEVAR (TV_PARSE_INMETH , "parser inl. meth. body")
Is it really important to distinguish this from other functions?
> -DEFTIMEVAR (TV_NAME_LOOKUP , "name lookup")
> -DEFTIMEVAR (TV_OVERLOAD , "overload resolution")
> -DEFTIMEVAR (TV_TEMPLATE_INSTANTIATION, "template instantiation")
> +DEFTIMEVAR (TV_INSTANTIATE_TEMPLATE , "instantiate template")
> +DEFTIMEVAR (TV_NAME_LOOKUP , "|name lookup")
> +DEFTIMEVAR (TV_RESOLVE_OVERLOAD , "|overload resolution")
Why these changes?
> @@ -564,6 +564,8 @@ compile_file (void)
> + timevar_start (TV_PHASE_PARSING);
Why does this happen before...
> + timevar_push (TV_PARSE_GLOBAL);
...this? I would think the bits in there should be part of _SETUP.
> @@ -16760,6 +16770,7 @@ cp_parser_class_specifier (cp_parser* parser)
> + timevar_pop (TV_PARSE_STRUCT);
> + timevar_pop (TV_PARSE_STRUCT);
> + timevar_pop (TV_PARSE_STRUCT);
> + timevar_pop (TV_PARSE_STRUCT);
Why not factor this out like you did with so many functions outside the
parser?
Jason
next prev parent reply other threads:[~2011-04-20 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 18:50 Lawrence Crowl
2011-04-12 19:06 ` Diego Novillo
2011-04-13 9:19 ` Richard Guenther
2011-04-13 20:57 ` Lawrence Crowl
2011-04-20 23:33 ` Jason Merrill [this message]
2011-04-21 20:38 ` Diego Novillo
2011-04-22 0:40 ` Lawrence Crowl
2011-04-22 2:34 ` Jason Merrill
2011-04-23 0:05 ` Lawrence Crowl
2011-04-24 9:34 ` Jason Merrill
2011-04-27 19:18 ` Lawrence Crowl
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=4DAF5782.90009@redhat.com \
--to=jason@redhat.com \
--cc=crowl@google.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=reply@codereview.appspotmail.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).