public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: gchare@google.com (Gabriel Charette)
To: reply@codereview.appspotmail.com, crowl@google.com,
	dnovillo@google.com,        gcc-patches@gcc.gnu.org
Subject: [pph] Removing unused timevars following pph instrumentation removal patch (issue4568053)
Date: Fri, 03 Jun 2011 17:29:00 -0000	[thread overview]
Message-ID: <20110603172857.85A491C3799@gchare.mtv.corp.google.com> (raw)

Removed the 3 PPH timevars used in pph instrumentation. Those are not used
anymore following the instrumentation removal patch.

Bootstrap build and regression testing were successful.

2011-06-03  Gabriel Charette  <gchare@google.com>

	* timevar.def (TV_PPH_CACHE_IN): Remove.
	(TV_PPH_CACHE_OUT): Remove.
	(TV_PPH_MANAGE): Remove.

Index: timevar.def
===================================================================
--- timevar.def	(revision 174568)
+++ timevar.def	(working copy)
@@ -69,11 +69,6 @@
 DEFTIMEVAR (TV_PTH_SKIP_TOKENS       , "PTH skip cached tokens")
 DEFTIMEVAR (TV_PTH_INIT              , "PTH initialization")
 
-/* Time spent handling PPH state.  */
-DEFTIMEVAR (TV_PPH_CACHE_IN          , "PPH cache in")
-DEFTIMEVAR (TV_PPH_CACHE_OUT         , "PPH cache out")
-DEFTIMEVAR (TV_PPH_MANAGE            , "PPH bookkeeping")
-
 DEFTIMEVAR (TV_CGRAPH                , "callgraph construction")
 DEFTIMEVAR (TV_CGRAPHOPT             , "callgraph optimization")
 DEFTIMEVAR (TV_VARPOOL               , "varpool construction")

--
This patch is available for review at http://codereview.appspot.com/4568053

             reply	other threads:[~2011-06-03 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 17:29 Gabriel Charette [this message]
2011-06-03 20:38 ` Diego Novillo

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=20110603172857.85A491C3799@gchare.mtv.corp.google.com \
    --to=gchare@google.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).