From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Jim Wilson <jimw@sifive.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] RISC-V: Correct legacy misa register number.
Date: Tue, 17 Jul 2018 15:40:00 -0000 [thread overview]
Message-ID: <20180717153957.GH2888@embecosm.com> (raw)
In-Reply-To: <CAFyWVaautDAVtJCnxmt0RHfEPrKFCuagnTXXbVhadwVcf5y4DQ@mail.gmail.com>
* Jim Wilson <jimw@sifive.com> [2018-07-16 15:01:41 -0700]:
> On Wed, Jul 4, 2018 at 1:34 AM, Andrew Burgess
> <andrew.burgess@embecosm.com> wrote:
> > * Jim Wilson <jimw@sifive.com> [2018-07-03 17:13:34 -0700]:
> >
> >> The main purpose of this patch is to fix the legacy misa register number, which
> >> is missing the +65 added to all of the other CSRs.
> >>
> >> This also changes DECLARE_CSR to use RISCV_FIRST_CSR_REGNUM instead of
> >> RISCV_LAST_FP_REGNUM+1 to be consistent with riscv-tdep.c.
> >>
> >> I don't have access to legacy hardware that I can test the misa number change
> >> with, but it has been tested on a riscv64-linux system using patched gdb and
> >> patched kernel, since it isn't usable otherwise.
> >>
> >> Jim
> >>
> >> gdb/
> >> * riscv-tdep.h (DECLARE_CSR): Use RISCV_FIRST_CSR_REGNUM instead of
> >> RISCV_LAST_FP_REGNUM + 1.
> >> (RSICV_CSR_LEGACY_MISA_REGNUM): Add RISCV_FIRST_CSR_REGNUM.
> >
> > Regardless of the discussion about RISCV_CSR_LEGACY_MISA_REGNUM
> > could you push the change to DECLARE_CSR anyway please. I think this
> > is a good clean up and it's unrelated to the other change.
>
> Tim Newsome confirmed that there should be no special behavior in
> OpenOCD to handle the legacy misa register number. I'd like approval
> to commit the whole patch. It is a bug fix for live code, and a minor
> consistency cleanup.
I approve then :)
Thanks,
Andrew
prev parent reply other threads:[~2018-07-17 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 0:14 Jim Wilson
2018-07-04 0:35 ` Palmer Dabbelt
2018-07-04 16:17 ` Jim Wilson
2018-07-06 3:16 ` Tim Newsome
[not found] ` <20180704083410.GD2675@embecosm.com>
2018-07-16 22:01 ` Jim Wilson
2018-07-17 15:40 ` Andrew Burgess [this message]
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=20180717153957.GH2888@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=jimw@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