From: Yao Qi <qiyaoltc@gmail.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Use code cache in aarch64 prologue analyzer
Date: Fri, 09 Dec 2016 09:40:00 -0000 [thread overview]
Message-ID: <20161209093954.GC13661@E107787-LIN> (raw)
In-Reply-To: <965901df-04c7-ab45-5e51-34afa9924559@codesourcery.com>
On 16-12-07 12:26:38, Luis Machado wrote:
> >
> >
>
> The series LGTM except for the nit in 1/3. FTR, we have a similar
> local patch for ARM and also PowerPC to get the performance numbers
> up a bit. It helps with remote debugging as well, since we can read
> from cache instead of fetching it over and over again from the
> target.
Yes, I still have some patches for ARM to use cache in arm-tdep.c.
I plan to send them out after I measured the performance improvement,
but I need to fix PR 20939 before 7.12.1 (released on Jan 2017), so
I won't post my ARM patches recently. If you already get your local
patches in shape, free feel to post them.
--
Yao (é½å°§)
next prev parent reply other threads:[~2016-12-09 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 15:04 [PATCH 0/3] Use code cache in arm and " Yao Qi
2016-12-06 15:04 ` [PATCH 3/3] Use code cache in " Yao Qi
2016-12-07 18:26 ` Luis Machado
2016-12-09 9:40 ` Yao Qi [this message]
2016-12-06 15:04 ` [PATCH 2/3] Use code cache in arm " Yao Qi
2016-12-06 15:04 ` [PATCH 1/3] Compile gdb.perf/skip-prologue.c with and without debug info Yao Qi
2016-12-07 18:24 ` Luis Machado
2016-12-09 9:56 ` Yao Qi
2016-12-09 9:57 ` [PATCH 0/3] Use code cache in arm and aarch64 prologue analyzer Yao Qi
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=20161209093954.GC13661@E107787-LIN \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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