From: Kito Cheng <kito.cheng@sifive.com>
To: gcc-patches@gcc.gnu.org, kito.cheng@gmail.com, jimw@sifive.com,
palmer@dabbelt.com, andrew@sifive.com
Subject: [PATCH 0/2] RISC-V: Vector extensions support
Date: Fri, 3 Dec 2021 23:50:52 +0800 [thread overview]
Message-ID: <20211203155054.52834-1-kito.cheng@sifive.com> (raw)
This patch set adding basic -march option support and feature test marco for
vector extensions, and also extend the syntax of arch string for vector
extensions, although that should change RISC-V ISA manual first would be
better, but we don't got response[1] yet, and that will block whole vector
extensions, so we decide fix that first.
[1] https://github.com/riscv/riscv-isa-manual/pull/718
next reply other threads:[~2021-12-03 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 15:50 Kito Cheng [this message]
2021-12-03 15:50 ` [PATCH 1/2] RISC-V: Allow extension name contain digit Kito Cheng
2022-01-06 16:57 ` Kito Cheng
2021-12-03 15:50 ` [PATCH 2/2] RISC-V: Minimal support of vector extensions Kito Cheng
2022-01-06 16:57 ` Kito Cheng
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=20211203155054.52834-1-kito.cheng@sifive.com \
--to=kito.cheng@sifive.com \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimw@sifive.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).