From: Nelson Chu <nelson.chu@sifive.com>
To: Binutils <binutils@sourceware.org>, gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
Andrew Waterman <andrew@sifive.com>,
asb@lowrisc.org, Kito Cheng <kito.cheng@sifive.com>,
Maxim Blinov <maxim.blinov@embecosm.com>,
Jim Wilson <jimw@sifive.com>,
Palmer Dabbelt <palmerdabbelt@google.com>
Subject: Re: [PATCH 1/7] RISC-V: Remove the redundant gas test file.
Date: Sat, 18 Apr 2020 19:20:18 +0800 [thread overview]
Message-ID: <CAJYME4EasQztWoKeHfP-QWjm7Dm_Qybj2qa9iH=HHMHnvtzdJw@mail.gmail.com> (raw)
In-Reply-To: <CAJYME4FnufEFyX+G9-5iu5vvR8hPe1u0uzjOHBfXCZQuc4eJKw@mail.gmail.com>
Miss Palmer again...
Very sorry for the redundant mails...
Nelson
On Sat, Apr 18, 2020 at 7:17 PM Nelson Chu <nelson.chu@sifive.com> wrote:
>
> CC Palmer.
>
> Thanks
> Nelson
>
> On Sat, Apr 18, 2020 at 7:08 PM Nelson Chu <nelson.chu@sifive.com> wrote:
> >
> > gas/
> > * testsuite/gas/riscv/march-fail-s-with-version: Removed.
> > ---
> > gas/testsuite/gas/riscv/march-fail-s-with-version | 2 --
> > 1 file changed, 2 deletions(-)
> > delete mode 100644 gas/testsuite/gas/riscv/march-fail-s-with-version
> >
> > diff --git a/gas/testsuite/gas/riscv/march-fail-s-with-version b/gas/testsuite/gas/riscv/march-fail-s-with-version
> > deleted file mode 100644
> > index a514d4a..0000000
> > --- a/gas/testsuite/gas/riscv/march-fail-s-with-version
> > +++ /dev/null
> > @@ -1,2 +0,0 @@
> > -Assembler messages:
> > -.*: Invalid or unknown s ISA extension: 'sfoo'
> > \ No newline at end of file
> > --
> > 2.7.4
> >
next prev parent reply other threads:[~2020-04-18 11:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 11:07 [PATCH 0/7] RISC-V: Support version controling for ISA standard extensions and CSR 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 [this message]
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
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='CAJYME4EasQztWoKeHfP-QWjm7Dm_Qybj2qa9iH=HHMHnvtzdJw@mail.gmail.com' \
--to=nelson.chu@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=andrew@sifive.com \
--cc=asb@lowrisc.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jimw@sifive.com \
--cc=kito.cheng@sifive.com \
--cc=maxim.blinov@embecosm.com \
--cc=palmerdabbelt@google.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).