From: Nelson Chu <nelson.chu@sifive.com>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: Binutils <binutils@sourceware.org>,
gdb-patches@sourceware.org, Alex Bradbury <asb@lowrisc.org>,
Kito Cheng <kito.cheng@sifive.com>
Subject: Re: [PATCH 0/7] RISC-V: Support version controling for ISA standard extensions and CSR
Date: Fri, 1 May 2020 17:29:00 +0800 [thread overview]
Message-ID: <CAJYME4E056Ex0eJe-Ni9L28L3vcE-4VEB0836KahgK-_UAtqew@mail.gmail.com> (raw)
In-Reply-To: <CA+yXCZA09cjPhWtN8Q0UcZkEbSWG1z2yUF8r4ZCEMnq+P8r-qQ@mail.gmail.com>
OK got it, I will fix this :)
Thanks
Nelson
On Fri, May 1, 2020 at 12:10 AM Kito Cheng <kito.cheng@gmail.com> wrote:
>
> >
> > * -misa-spec = [2p0|2p1|2p2|20190608|20191213]
> > You can simply choose the ISA spec by this option, and then assembler will set
> > the version for the standard extensions if you don’t set in the ELF arch
> > attributes or -march option.
>
> Could you change this into 2.0|2.1|... instead of 2p0|2p1|... ?
> Unlike arch string has specified by spec, it must use `p` instead of `.`.
> so I think there is no necessary to use `p` here.
>
> > * --with-isa-spec = [2p0|2p1|2p2|20190608|20191213]
> > The syntax is same as -misa-spec option. Assembler will check this if
> > -misa-spec option isn’t set.
>
> Same comment as -misa-spec.
>
> > * -mpriv-spec=[1p9|1p9p1|1p10|1p11]
> > This is used to set the privileged spec’s version, and we can decide whether
> > the CSR is valid or not.
>
> Change to 1.9 instead of 1p9.
>
> >
> > === New Default Configure Option ===
> >
> > * --with-priv-spec = [1p9|1p9p1|1p10|1p11]
>
> Same comment as -mpriv-spec=
prev parent reply other threads:[~2020-05-01 9:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 11:07 Nelson Chu
2020-04-18 11:07 ` [PATCH 1/7] RISC-V: Remove the redundant gas test file Nelson Chu
2020-04-18 11:17 ` Nelson Chu
2020-04-18 11:20 ` Nelson Chu
2020-04-18 11:07 ` [PATCH 2/7] RISC-V: Forgot to update the priv-reg-fail-read-only-01 test case Nelson Chu
2020-04-18 11:17 ` Nelson Chu
2020-04-18 11:07 ` [PATCH 3/7] RISC-V: Support new GAS options and configure options to set ISA versions Nelson Chu
2020-04-18 11:18 ` Nelson Chu
2020-04-23 22:58 ` Palmer Dabbelt
2020-04-24 2:37 ` Nelson Chu
2020-04-24 6:43 ` Nelson Chu
2020-04-18 11:07 ` [PATCH 4/7] RISC-V: Support version checking for CSR according to privilege version Nelson Chu
2020-04-18 11:18 ` Nelson Chu
2020-04-24 10:21 ` Andrew Burgess
2020-04-27 1:35 ` Nelson Chu
2020-04-18 11:07 ` [PATCH 5/7] RISC-V: Make privilege spec attributes work Nelson Chu
2020-04-18 11:18 ` Nelson Chu
2020-04-18 11:07 ` [PATCH 6/7] RISC-V: Disassembler dumps the CSR according to the chosen privilege spec Nelson Chu
2020-04-18 11:18 ` Nelson Chu
2020-04-18 11:07 ` [PATCH 7/7] RISC-V: Add documents and --help for the new GAS and OBJDUMP options Nelson Chu
2020-04-18 11:19 ` Nelson Chu
2020-04-18 11:17 ` [PATCH 0/7] RISC-V: Support version controling for ISA standard extensions and CSR Nelson Chu
2020-04-23 20:59 ` Palmer Dabbelt
2020-04-30 16:10 ` Kito Cheng
2020-05-01 9:29 ` Nelson Chu [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=CAJYME4E056Ex0eJe-Ni9L28L3vcE-4VEB0836KahgK-_UAtqew@mail.gmail.com \
--to=nelson.chu@sifive.com \
--cc=asb@lowrisc.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@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).