public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Basile Starynkevitch <basile@starynkevitch.net>, jit@gcc.gnu.org
Subject: Re: JIT compilation speed
Date: Thu, 01 Jan 2015 00:00:00 -0000	[thread overview]
Message-ID: <CACXZuxdwXd11Ap63r9RYCujAm2EqxxFqptmbCzzi2c5HQE5=ug@mail.gmail.com> (raw)
In-Reply-To: <1438647513.21752.13.camel@surprise>

On 4 August 2015 at 01:18, David Malcolm <dmalcolm@redhat.com> wrote:
> FWIW, the timer patch:
>  https://gcc.gnu.org/ml/gcc-patches/2015-07/msg02715.html
> is now in trunk (r226530).
>
> So if you're using trunk, you should be able to:
>
>   /* One-time initialization. */
>   gcc_jit_timer *timer = gcc_jit_timer_new ();
>
>
>
>   /* For all of your contexts, have them all use the
>      same shared timer:  */
>   gcc_jit_context_set_timer (ctxt, timer);
>
>
>
>   /* On shutdown, print the accumulated timings.  */
>   gcc_jit_timer_print (timer, stderr);
>   gcc_jit_timer_release (timer);
>
> to get a profile on stderr of where all that time is being spent.
>

Thanks Dave. I am currently tied up with nailing down an elusive bug
in Ravi - and have not had time to look at libgccjit related work. But
I hope to get back to it soon. Will keep you posted.

Regards
Dibyendu

  reply	other threads:[~2015-08-05 19:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01  0:00 Dibyendu Majumdar
2015-01-01  0:00 ` David Malcolm
2015-01-01  0:00   ` Basile Starynkevitch
2015-01-01  0:00     ` David Malcolm
2015-01-01  0:00     ` Dibyendu Majumdar
2015-01-01  0:00       ` David Malcolm
2015-01-01  0:00         ` Dibyendu Majumdar [this message]
2015-01-01  0:00       ` Basile Starynkevitch
2015-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='CACXZuxdwXd11Ap63r9RYCujAm2EqxxFqptmbCzzi2c5HQE5=ug@mail.gmail.com' \
    --to=mobile@majumdar.org.uk \
    --cc=basile@starynkevitch.net \
    --cc=dmalcolm@redhat.com \
    --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).