From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Cc: arnez@linux.vnet.ibm.com
Subject: [PATCH 0/2] Add DW_OP_implicit_value in dwarf assembler
Date: Tue, 24 Jan 2017 09:42:00 -0000 [thread overview]
Message-ID: <1485250945-17594-1-git-send-email-yao.qi@linaro.org> (raw)
In-Reply-To: <m3shoevrkf.fsf@oc1027705133.ibm.com>
Andreas posted a patch
https://sourceware.org/ml/gdb-patches/2017-01/msg00251.html and added
DW_OP_implicit_value in dwarf assembler. I find DW_OP_implicit_value
can be used in gdb.dwarf2/implptr-64bit.exp, so that we can remove
implptr-64bit.S and use the generated .S file instead.
Patch 1 fixes a minor bug in dwarf assembler, and patch 2 does the
major work. Run gdb.dwarf2/*.exp on i686-pc-linux-gnu. There is
no change in the .S files generated by dwarf assembler.
*** BLURB HERE ***
Yao Qi (2):
Handle DW_OP_GNU_implicit_pointer in dwarf assembler
Use dwarf assembler in gdb.dwarf2/implptr-64bit.exp
gdb/testsuite/gdb.dwarf2/implptr-64bit.S | 226 -----------------------------
gdb/testsuite/gdb.dwarf2/implptr-64bit.exp | 118 +++++++++++++--
gdb/testsuite/lib/dwarf.exp | 46 +++++-
3 files changed, 153 insertions(+), 237 deletions(-)
delete mode 100644 gdb/testsuite/gdb.dwarf2/implptr-64bit.S
--
1.9.1
next prev parent reply other threads:[~2017-01-24 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 19:24 [PATCH] Big-endian targets: don't ignore offset into DW_OP_implicit_value Andreas Arnez
2017-01-19 17:44 ` Yao Qi
2017-01-19 18:21 ` Andreas Arnez
2017-01-24 9:42 ` Yao Qi [this message]
2017-01-24 9:43 ` [PATCH 2/2] Use dwarf assembler in gdb.dwarf2/implptr-64bit.exp Yao Qi
2017-01-24 19:21 ` Andreas Arnez
2017-01-25 16:26 ` Yao Qi
2017-01-24 9:43 ` [PATCH 1/2] Handle DW_OP_GNU_implicit_pointer in dwarf assembler Yao Qi
2017-01-25 22:12 ` [PATCH] Big-endian targets: don't ignore offset into DW_OP_implicit_value Yao Qi
2017-01-27 19:35 ` Andreas Arnez
2017-02-01 9:09 ` Andreas Arnez
2017-02-01 9:16 ` 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=1485250945-17594-1-git-send-email-yao.qi@linaro.org \
--to=qiyaoltc@gmail.com \
--cc=arnez@linux.vnet.ibm.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