From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/4] Fix gdb.trace/entry-values.exp fails in thumb mode
Date: Fri, 11 Jul 2014 07:34:00 -0000 [thread overview]
Message-ID: <53BF7680.2010505@codesourcery.com> (raw)
In-Reply-To: <1404367792-23234-1-git-send-email-yao@codesourcery.com>
On 07/03/2014 02:09 PM, Yao Qi wrote:
> We see some fails in gdb.trace/entry-values.exp in thumb mode
> (-mthumb -march={armv4t,armv7-a}), which are caused by two problems in
> gdb,
>
> - prologue analysis in gdb for thumb code is broken. Patch #3 is to
> fix it by stopping prologue analysis when it goes to the epilogue.
> - dwarf assembler in gdb.trace/entry-values.exp uses functions whose
> address's bit 0 is set, which is incorrect. Patch #4 is to fix it.
>
> Patch 1 is preparatory patch and patch 2 is a refactor one. Each of them
> is regression tested on arm-none-linux-gnueabi.
Ping. Patch 4 was approved by Joel and was pushed in, but patches 1~3
still need approval.
--
Yao (é½å°§)
prev parent reply other threads:[~2014-07-11 5:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 6:11 Yao Qi
2014-07-03 6:11 ` [PATCH 3/4] Stop prologue analysis when past the epilogue Yao Qi
2014-07-03 8:39 ` Will Newton
2014-07-11 13:39 ` Joel Brobecker
2014-07-03 6:11 ` [PATCH 2/4] Match instruction adjusts SP in thumb Yao Qi
2014-07-03 8:35 ` Will Newton
2014-07-11 13:25 ` Joel Brobecker
2014-09-24 12:56 ` Yao Qi
2014-07-03 6:11 ` [PATCH 1/4] Restrict matching add/sub sp, #imm Yao Qi
2014-07-03 8:31 ` Will Newton
2014-07-07 1:38 ` Yao Qi
2014-07-11 13:25 ` Joel Brobecker
2014-07-11 13:49 ` Yao Qi
2014-07-03 6:11 ` [PATCH 4/4] Fix gdb.trace/entry-values.exp for thumb mode Yao Qi
2014-07-07 15:15 ` Joel Brobecker
2014-07-08 8:53 ` Yao Qi
2014-07-11 7:34 ` Yao Qi [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=53BF7680.2010505@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