From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Cc: monk.chiang <monk.chiang@sifive.com>, kito.cheng <kito.cheng@gmail.com>
Subject: [PATCH v2] RISC-V: Support scheduling for sifive p600 series
Date: Thu, 1 Feb 2024 11:07:48 +0800 [thread overview]
Message-ID: <AAE6E5B136EA7E37+202402011107474289218@rivai.ai> (raw)
[-- Attachment #1: Type: text/plain, Size: 133 bytes --]
Hi, Monk.
This model doesn't include vector. Will you add vector pipeline in the followup patches ?
juzhe.zhong@rivai.ai
next reply other threads:[~2024-02-01 3:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 3:07 juzhe.zhong [this message]
2024-02-01 8:10 ` Monk Chiang
2024-02-01 8:13 ` juzhe.zhong
2024-02-01 12:55 ` Kito Cheng
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 3:01 Monk Chiang
2024-02-01 12:53 ` 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=AAE6E5B136EA7E37+202402011107474289218@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.com \
--cc=monk.chiang@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).