From: Yichao Yu <yyc1992@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org, Paul Pluzhnikov <ppluzhnikov@google.com>
Subject: Re: JIT debugging (Attach and speed)
Date: Wed, 23 Mar 2016 20:51:00 -0000 [thread overview]
Message-ID: <CAMvDr+S1h46g=dxnKP5UBGrVnSfrf=S84ZmNtE4LU_D1SUKBXw@mail.gmail.com> (raw)
In-Reply-To: <56F2F31F.4000104@redhat.com>
On Wed, Mar 23, 2016 at 3:48 PM, Pedro Alves <palves@redhat.com> wrote:
> On 03/23/2016 07:32 PM, Yichao Yu wrote:
>
>>> So, as a quick hack, if you make inline_frame_sniffer bail out early
>>> with 0, does it improve things?
>>
>
>> The timing looks the same. =(
>
> Bummer. :-/
>
> Having now looked at the gdb.base/jit.exp test, I see that
> we can easily reproduce this with:
>
> gdb ---args ./testsuite/outputs/gdb.base/jit/jit-main ./testsuite/outputs/gdb.base/jit/jit-solib.so 2000
>
> (It'd be nice to turn this into a check-perf test...)
The new profile after disabling that line[1].
Am I reading it correctly that it skips the one I disabled and fails
to the next option which is basically as expensive?
Also, it looks like gdb is trying to get info about the current frame?
Can this be disabled for this breakpoint since it's not a "real" one?
[1] http://i.imgur.com/NHdoka8.jpg
>
>> What do you mean by "loader"? since you mentioned call JIT_REGISTER I
>> assume you mean JIT compiler?
>
> Yes, sorry. I meant whatever code ends up "sending" a JIT_REGISTER
> event to gdb.
>
> Thanks,
> Pedro Alves
>
next prev parent reply other threads:[~2016-03-23 20:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 14:56 Yichao Yu
2016-03-22 15:46 ` Pedro Alves
2016-03-22 16:10 ` Paul Pluzhnikov
2016-03-22 16:15 ` Pedro Alves
2016-03-22 16:23 ` Yichao Yu
2016-03-22 16:41 ` Pedro Alves
2016-03-22 16:47 ` Yichao Yu
2016-03-22 17:00 ` Pedro Alves
2016-03-23 2:18 ` Yichao Yu
2016-03-23 4:51 ` Yichao Yu
2016-03-23 18:24 ` Pedro Alves
2016-03-23 19:32 ` Yichao Yu
2016-03-23 19:48 ` Pedro Alves
2016-03-23 20:51 ` Yichao Yu [this message]
2016-03-24 1:17 ` Pedro Alves
2016-03-24 3:14 ` Yichao Yu
2016-03-24 21:02 ` Yichao Yu
2016-03-23 12:24 ` Pedro Alves
2016-03-23 13:31 ` Pedro Alves
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='CAMvDr+S1h46g=dxnKP5UBGrVnSfrf=S84ZmNtE4LU_D1SUKBXw@mail.gmail.com' \
--to=yyc1992@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=ppluzhnikov@google.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