Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Use code cache in arm and aarch64 prologue analyzer
Date: Tue, 06 Dec 2016 15:04:00 -0000	[thread overview]
Message-ID: <1481036629-21542-1-git-send-email-yao.qi@linaro.org> (raw)

This patch series improves the speed on setting a breakpoint on a
function, like "break foo" on arm and aarch64.  Each backend has
slightly different paths on "debug information exists vs. debug
information doesn't exist".  Patch #1 changes gdb.perf/skip-prologue.exp
so that we can compile the test case with and without debug
information.  Patch #2 and patch #3 improves arm and aarch respectively.

*** BLURB HERE ***

Yao Qi (3):
  Compile gdb.perf/skip-prologue.c with and without debug info
  Use code cache in arm prologue analyzer
  Use code cache in aarch64 prologue analyzer

 gdb/aarch64-tdep.c                       |  2 +-
 gdb/arm-tdep.c                           | 38 ++++++++++++++++----------------
 gdb/testsuite/gdb.perf/skip-prologue.exp |  8 ++++++-
 3 files changed, 27 insertions(+), 21 deletions(-)

-- 
1.9.1


             reply	other threads:[~2016-12-06 15:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 15:04 Yao Qi [this message]
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-06 15:04 ` [PATCH 2/3] Use code cache in arm prologue analyzer Yao Qi
2016-12-06 15:04 ` [PATCH 3/3] Use code cache in aarch64 " Yao Qi
2016-12-07 18:26   ` Luis Machado
2016-12-09  9:40     ` Yao Qi
2016-12-09  9:57 ` [PATCH 0/3] Use code cache in arm and " 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=1481036629-21542-1-git-send-email-yao.qi@linaro.org \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.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