From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: jimw@sifive.com, palmer@sifive.com, jhb@FreeBSD.org,
Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH 0/2] RISC-V Prologue Scan And Test Improvement
Date: Mon, 05 Nov 2018 23:10:00 -0000 [thread overview]
Message-ID: <cover.1541459121.git.andrew.burgess@embecosm.com> (raw)
Two patches that are unrelated other than being RISC-V related.
--
Andrew Burgess (2):
gdb/riscv: Stop prologue scan if instruction fetch/decode fails
gdb/riscv: Update test to support targets without FP hardware
gdb/ChangeLog | 6 ++++++
gdb/riscv-tdep.c | 27 ++++++++++++++++++++++++---
gdb/testsuite/ChangeLog | 5 +++++
gdb/testsuite/gdb.arch/riscv-reg-aliases.exp | 24 ++++++++++++++++++------
4 files changed, 53 insertions(+), 9 deletions(-)
--
2.14.5
next reply other threads:[~2018-11-05 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 23:10 Andrew Burgess [this message]
2018-11-05 23:10 ` [PATCH 2/2] gdb/riscv: Update test to support targets without FP hardware Andrew Burgess
2018-11-05 23:10 ` [PATCH 1/2] gdb/riscv: Stop prologue scan if instruction fetch/decode fails Andrew Burgess
2018-11-05 23:37 ` Jim Wilson
2018-11-06 11:18 ` Andrew Burgess
2018-11-06 19:40 ` Jim Wilson
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.1541459121.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=jimw@sifive.com \
--cc=palmer@sifive.com \
/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