From: John Baldwin <jhb@FreeBSD.org>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] RISC-V fflags, frm, and fcsr (includes small tdesc change)
Date: Tue, 16 Aug 2022 09:26:44 -0700 [thread overview]
Message-ID: <1490be1e-92fc-7845-6f24-5c5358915d1d@FreeBSD.org> (raw)
In-Reply-To: <cover.1660644464.git.aburgess@redhat.com>
On 8/16/22 3:09 AM, Andrew Burgess via Gdb-patches wrote:
> 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
I only skimmed the patches, but I agree that the idea of using pseudo registers
for frm and fflags unless a remote target provides them explicitly is the
right approach.
--
John Baldwin
next prev parent reply other threads:[~2022-08-16 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 10:09 Andrew Burgess via Gdb-patches
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 ` John Baldwin [this message]
2022-08-31 15:33 ` [PATCH 0/3] RISC-V fflags, frm, and fcsr (includes small tdesc change) 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=1490be1e-92fc-7845-6f24-5c5358915d1d@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=aburgess@redhat.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