qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: liuzhiwei <zhiwei_liu@c-sky.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: palmer@sifive.com, Alistair.Francis@wdc.com,
	sagark@eecs.berkeley.edu, bastian@mail.uni-paderborn.de
Subject: [Qemu-devel] RISC-V: Vector && DSP Extension
Date: Thu, 8 Aug 2019 17:39:47 +0800	[thread overview]
Message-ID: <97a6ae9f-2845-4a3c-2a31-367787622268@c-sky.com> (raw)

Hi all,

    My workmate  and I have been working on Vector & Dsp extension, and 
I'd like to share develop status  with folks.

    The spec references for  Vector extension is riscv-v-spec-0.7.1, and 
riscv-p-spec-0.5 for DSP extension. The code of vector extension is 
ready and under testing,  the first patch will be sent about two weeks 
later. After that we will forward working on DSP extension, and send the 
first patch in middle  October.

     Could the maintainers  tell me whether the specs referenced are 
appropriate? Is anyone working on these extensions?  I'd like to get 
your status, and maybe discuss questions and work togather.

Best Regards

LIU Zhiwei




             reply	other threads:[~2019-08-08  9:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  9:39 liuzhiwei [this message]
2019-08-08 11:29 ` [Qemu-devel] RISC-V: Vector && DSP Extension Aleksandar Markovic
2019-08-08 13:48   ` Chih-Min Chao
2019-08-08 14:19     ` Aleksandar Markovic
2019-08-10 13:35     ` LIU ZhiWei
2019-08-10  1:54 ` Alistair Francis
2019-08-10 13:55   ` LIU ZhiWei
2019-08-11 16:50     ` Alistair Francis
2019-08-15  8:53       ` Aleksandar Markovic
2019-08-15  9:07         ` Peter Maydell
2019-08-15 10:32           ` Aleksandar Markovic
2019-08-15 21:37           ` Alistair Francis
2019-08-21 19:31             ` Palmer Dabbelt
2019-08-21 23:10               ` [Qemu-devel] [Qemu-riscv] " Jonathan Behrens
2019-08-22  1:50               ` [Qemu-devel] " liuzhiwei
2019-08-22 22:37                 ` Alistair Francis
2019-08-28  0:25                   ` Palmer Dabbelt

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=97a6ae9f-2845-4a3c-2a31-367787622268@c-sky.com \
    --to=zhiwei_liu@c-sky.com \
    --cc=Alistair.Francis@wdc.com \
    --cc=bastian@mail.uni-paderborn.de \
    --cc=palmer@sifive.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=sagark@eecs.berkeley.edu \
    /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 NNTP newsgroup(s).