From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/2] Fix fails in dw2-dir-file-name.exp on arm
Date: Sun, 30 Nov 2014 03:40:00 -0000 [thread overview]
Message-ID: <1417318831-1522-1-git-send-email-yao@codesourcery.com> (raw)
I see many fails in dw2-dir-file-name.exp on arm target, and this patch
series is to fix them. Patch 2 does the fix and patch 1 is a preparatory
patch. Without patch 1, patch 2 will cause regressions. See details
from each.
These patches are tested on arm-linux-gnueabi in both arm mode and thumb
mode.
*** BLURB HERE ***
Yao Qi (2):
Don't scan prologue past epilogue
Improve arm_skip_prologue by using arm_analyze_prologue
gdb/arm-tdep.c | 128 +++++++++++++++++++--------------------------------------
1 file changed, 43 insertions(+), 85 deletions(-)
--
1.9.3
next reply other threads:[~2014-11-30 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 3:40 Yao Qi [this message]
2014-11-30 3:40 ` [PATCH 2/2] Improve arm_skip_prologue by using arm_analyze_prologue Yao Qi
2014-11-30 3:40 ` [PATCH 1/2] Don't scan prologue past epilogue Yao Qi
2014-12-12 0:51 ` [PATCH 0/2] Fix fails in dw2-dir-file-name.exp on arm 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=1417318831-1522-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).