From: David Malcolm <dmalcolm@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: jit@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [RFA jit 2/2] introduce scoped_timevar
Date: Wed, 01 Jan 2014 00:00:00 -0000 [thread overview]
Message-ID: <1395176728.28037.107.camel@surprise> (raw)
In-Reply-To: <1395154664-29657-3-git-send-email-tromey@redhat.com>
On Tue, 2014-03-18 at 08:57 -0600, Tom Tromey wrote:
> This introduces a new scoped_timevar class. It pushes a given timevar
> in its constructor, and pops it in the destructor, giving a much
> simpler way to use timevars in the typical case where they can be
> scoped.
> ---
> gcc/ChangeLog.jit | 4 ++++
> gcc/jit/ChangeLog.jit | 4 ++++
> gcc/jit/internal-api.c | 16 +++++-----------
> gcc/timevar.h | 24 +++++++++++++++++++++++-
> 4 files changed, 36 insertions(+), 12 deletions(-)
Thanks. Looks good to me, but, like the other patch, are the
ChangeLog.jit entries available somewhere?
next prev parent reply other threads:[~2014-03-18 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 0:00 [RFA jit 0/2] minor refactorings for reuse Tom Tromey
2014-01-01 0:00 ` [RFA jit 2/2] introduce scoped_timevar Tom Tromey
2014-01-01 0:00 ` David Malcolm [this message]
2014-01-01 0:00 ` [RFA jit 1/2] introduce class toplev Tom Tromey
2014-01-01 0:00 ` David Malcolm
2014-01-01 0:00 ` Tom Tromey
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=1395176728.28037.107.camel@surprise \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jit@gcc.gnu.org \
--cc=tromey@redhat.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).