From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/3] RISC-V fflags, frm, and fcsr (includes small tdesc change)
Date: Tue, 16 Aug 2022 11:09:55 +0100 [thread overview]
Message-ID: <cover.1660644464.git.aburgess@redhat.com> (raw)
While testing on a RISC-V native Linux target, I noticed some issues
accessing the fflags and frm registers. This series addresses these issues.
Patch #2 is a small extension to the target description mechanism
required to support patch #3.
Thanks,
Andrew
---
Andrew Burgess (3):
gdb/riscv: improve (and fix) display of frm field in 'info registers'
gdb: Add tdesc_found_register function to tdesc API
gdb/riscv: better support for fflags and frm registers
gdb/arch/riscv.h | 19 +-
gdb/features/riscv/32bit-fpu.c | 4 +-
gdb/features/riscv/32bit-fpu.xml | 2 -
gdb/features/riscv/64bit-fpu.c | 4 +-
gdb/features/riscv/64bit-fpu.xml | 2 -
gdb/riscv-tdep.c | 236 +++++++++++++++---
gdb/riscv-tdep.h | 6 +
gdb/target-descriptions.c | 11 +
gdb/target-descriptions.h | 4 +
gdb/testsuite/gdb.arch/riscv-info-fcsr.c | 22 ++
gdb/testsuite/gdb.arch/riscv-info-fcsr.exp | 149 +++++++++++
.../gdb.arch/riscv-tdesc-fcsr-32.xml | 75 ++++++
.../gdb.arch/riscv-tdesc-fcsr-64.xml | 79 ++++++
.../gdb.arch/riscv-tdesc-loading-05.xml | 77 ++++++
.../gdb.arch/riscv-tdesc-loading-06.xml | 75 ++++++
gdb/testsuite/gdb.arch/riscv-tdesc-regs.exp | 36 +++
16 files changed, 755 insertions(+), 46 deletions(-)
create mode 100644 gdb/testsuite/gdb.arch/riscv-info-fcsr.c
create mode 100644 gdb/testsuite/gdb.arch/riscv-info-fcsr.exp
create mode 100644 gdb/testsuite/gdb.arch/riscv-tdesc-fcsr-32.xml
create mode 100644 gdb/testsuite/gdb.arch/riscv-tdesc-fcsr-64.xml
create mode 100644 gdb/testsuite/gdb.arch/riscv-tdesc-loading-05.xml
create mode 100644 gdb/testsuite/gdb.arch/riscv-tdesc-loading-06.xml
--
2.25.4
next reply other threads:[~2022-08-16 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 10:09 Andrew Burgess via Gdb-patches [this message]
2022-08-16 10:09 ` [PATCH 1/3] gdb/riscv: improve (and fix) display of frm field in 'info registers' Andrew Burgess via Gdb-patches
2022-08-16 10:09 ` [PATCH 2/3] gdb: Add tdesc_found_register function to tdesc API Andrew Burgess via Gdb-patches
2022-08-16 10:09 ` [PATCH 3/3] gdb/riscv: better support for fflags and frm registers Andrew Burgess via Gdb-patches
2022-08-31 15:11 ` Andrew Burgess via Gdb-patches
2022-08-16 16:26 ` [PATCH 0/3] RISC-V fflags, frm, and fcsr (includes small tdesc change) John Baldwin
2022-08-31 15:33 ` Andrew Burgess via Gdb-patches
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.1660644464.git.aburgess@redhat.com \
--to=gdb-patches@sourceware.org \
--cc=aburgess@redhat.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