From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Nelson Chu <nelson.chu@sifive.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] RISC-V: Update the rebuild-csr-xml.sh.
Date: Thu, 11 Jun 2020 15:07:19 +0100 [thread overview]
Message-ID: <20200611140719.GL2737@embecosm.com> (raw)
In-Reply-To: <1591851205-10870-1-git-send-email-nelson.chu@sifive.com>
* Nelson Chu <nelson.chu@sifive.com> [2020-06-10 21:53:25 -0700]:
> We add new arguments defined and aborted verisons for DECLARE_CSR to
> support privileged versions controling in binutils. Therefore, the
> rebuild-csr-xml.sh should be updated, too.
>
> gdb/
> * features/riscv/rebuild-csr-xml.sh: Updated.
LGTM.
Thanks,
Andrew
> ---
> gdb/features/riscv/rebuild-csr-xml.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/features/riscv/rebuild-csr-xml.sh b/gdb/features/riscv/rebuild-csr-xml.sh
> index 1adb180..bff79b0 100755
> --- a/gdb/features/riscv/rebuild-csr-xml.sh
> +++ b/gdb/features/riscv/rebuild-csr-xml.sh
> @@ -22,12 +22,12 @@ EOF
> if [ "$bitsize" = "64" ]; then
> grep "^DECLARE_CSR(" ${RISCV_OPC_FILE} \
> | sed /CSR_CLASS_.*_32/d \
> - | sed -e "s!DECLARE_CSR(\(.*\), .*, .*! <reg name=\"\1\" bitsize=\"$bitsize\"/>!"
> + | sed -e "s!DECLARE_CSR(\(.*\), .*, .*, .*, .*! <reg name=\"\1\" bitsize=\"$bitsize\"/>!"
>
> echo "</feature>"
> else
> grep "^DECLARE_CSR(" ${RISCV_OPC_FILE} \
> - | sed -e "s!DECLARE_CSR(\(.*\), .*, .*! <reg name=\"\1\" bitsize=\"$bitsize\"/>!"
> + | sed -e "s!DECLARE_CSR(\(.*\), .*, .*, .*, .*! <reg name=\"\1\" bitsize=\"$bitsize\"/>!"
>
> echo "</feature>"
> fi
> --
> 2.7.4
>
next prev parent reply other threads:[~2020-06-11 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 4:53 Nelson Chu
2020-06-11 14:07 ` Andrew Burgess [this message]
2020-06-12 1:45 ` Nelson Chu
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=20200611140719.GL2737@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=nelson.chu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).