From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simark@simark.ca>, Eli Zaretskii <eliz@gnu.org>,
Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCHv3 0/2] Initial RiscV Support
Date: Fri, 02 Mar 2018 20:09:00 -0000 [thread overview]
Message-ID: <cover.1520021226.git.andrew.burgess@embecosm.com> (raw)
In-Reply-To: <1b9ec42a-a0fd-667b-59a5-780e84cce451@simark.ca>
Things that have changed in this revision:
1. Now use an observer to clear the inferior data when an inferior
exits. This is a pretty common pattern for other users of the
inferior data.
2. I've made small code clean ups suggested by Simon.
3. Switched to new/delete as suggested.
4. I've made the riscv test I added a generic test. The test was
added to cover a RiscV case, but there's really no reason it had
to be RiscV only. Once I tested this on x86-64 I hit a bug in
the argument passing on that target, which is fixed in the new
first patch of this series.
5. Rebased onto master as of yesterday and retested on all 8 RiscV
variants. Still getting the same pass rate as before. Also
tested on x86-64 GNU/Linux with no regressions.
Thanks,
Andrew
--
Andrew Burgess (2):
gdb/amd64: Ignore zero sized fields when calling functions
gdb: Initial baremetal riscv support
gdb/ChangeLog | 19 +
gdb/MAINTAINERS | 5 +
gdb/Makefile.in | 3 +
gdb/NEWS | 4 +
gdb/amd64-tdep.c | 5 +-
gdb/configure.tgt | 5 +
gdb/riscv-tdep.c | 2749 +++++++++++++++++++++++++++++
gdb/riscv-tdep.h | 84 +
gdb/testsuite/ChangeLog | 6 +
gdb/testsuite/gdb.base/float.exp | 2 +
gdb/testsuite/gdb.base/nested-structs.c | 159 ++
gdb/testsuite/gdb.base/nested-structs.exp | 189 ++
12 files changed, 3228 insertions(+), 2 deletions(-)
create mode 100644 gdb/riscv-tdep.c
create mode 100644 gdb/riscv-tdep.h
create mode 100644 gdb/testsuite/gdb.base/nested-structs.c
create mode 100644 gdb/testsuite/gdb.base/nested-structs.exp
--
2.14.3
next prev parent reply other threads:[~2018-03-02 20:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 19:15 [PATCH] gdb: Initial baremetal riscv support Andrew Burgess
2018-02-13 19:49 ` Eli Zaretskii
2018-02-19 20:01 ` Simon Marchi
2018-02-27 1:09 ` [PATCHv2] " Andrew Burgess
2018-02-27 3:33 ` Simon Marchi
2018-03-02 20:09 ` Andrew Burgess [this message]
2018-03-02 20:10 ` [PATCHv3 1/2] gdb/amd64: Ignore zero sized fields when calling functions Andrew Burgess
2018-03-03 6:29 ` Simon Marchi
2018-03-02 20:10 ` [PATCHv3 2/2] gdb: Initial baremetal riscv support Andrew Burgess
2018-03-03 6:27 ` Simon Marchi
2018-03-05 10:46 ` [PATCHv4 " Andrew Burgess
2018-03-05 22:35 ` Simon Marchi
2018-03-06 11:06 ` Yao Qi
2018-03-06 11:35 ` Yao Qi
2018-03-03 7:40 ` [PATCHv3 " Eli Zaretskii
2018-02-27 3:37 ` [PATCHv2] " Simon Marchi
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=cover.1520021226.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).