From: Fredrik Tolf <fredrik@dolda2000.com>
To: Pedro Alves <palves@redhat.com>, gdb@sourceware.org
Subject: Re: Bad performance in updating JIT debug symbols
Date: Tue, 20 Sep 2016 02:20:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.11.1609200414180.2866@shack.dolda2000.com> (raw)
In-Reply-To: <b2ec4cc4-394a-a532-ea0e-bf2a4da4f7f9@redhat.com>
On Mon, 19 Sep 2016, Pedro Alves wrote:
> I've now rebased and force-pushed part of what I had to the
> users/palves/jit-speedup branch. It's regression-free for me
> on x86_64 Fedora 23. I'm also attaching qsort patch below for
> reference.
I tested the branch, and can verify that it seems to be working really
well for me. I no longer any noticable slowdown at compilations
whatsoever, so that's really great for me. I'll probably be running this
until the code gets its way into release, so thanks a lot!
I haven't tested it a whole lot yet, but I too haven't noticed any
regressions thus far.
> If you don't have any breakpoint set, then with that branch,
> JIT debugging is snappy. The problem is that the next bottleneck
> triggers as soon as you have some breakpoint set.
For the record, I'm not noticing this. I tried setting a breakpoint, and
there's still no problem whatsoever when new code is JITted.
--
Fredrik Tolf
prev parent reply other threads:[~2016-09-20 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 17:25 Fredrik Tolf
[not found] ` <F4715250-E24B-452E-9232-2469AB2EB2B2@duaneellis.com>
2016-09-17 18:43 ` Fredrik Tolf
2016-09-18 13:55 ` Yichao Yu
2016-09-19 15:10 ` Pedro Alves
2016-09-19 15:45 ` Yichao Yu
2016-09-20 2:20 ` Fredrik Tolf [this message]
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=alpine.DEB.2.11.1609200414180.2866@shack.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=gdb@sourceware.org \
--cc=palves@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