From: Tom Tromey <tromey@redhat.com>
To: jit@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: [RFA jit 0/2] minor refactorings for reuse
Date: Wed, 01 Jan 2014 00:00:00 -0000 [thread overview]
Message-ID: <1395154664-29657-1-git-send-email-tromey@redhat.com> (raw)
I wanted to do something like playback::context::compile, but in my
project I can't really reuse all the JIT code -- really I just wanted
to be able to use toplev_main and toplev_finalize.
Looking into the code, though, I saw a few spots that could be cleaned
up a little, so I wouldn't have to worry as much about keeping my
hacks in sync with the JIT branch.
The first patch here changes the toplev code into a class and arranges
for the timevars to be managed there.
The second patch just introduces scoped timevars to make them less
error-prone to use.
I built and tested this using the JIT test suite.
Let me know what you think,
Tom
next reply other threads:[~2014-03-18 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 0:00 Tom Tromey [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
2014-01-01 0:00 ` [RFA jit 2/2] introduce scoped_timevar Tom Tromey
2014-01-01 0:00 ` David Malcolm
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=1395154664-29657-1-git-send-email-tromey@redhat.com \
--to=tromey@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jit@gcc.gnu.org \
/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).