From: =?gb18030?B?1tO+09Xc?= <juzhe.zhong@rivai.ai>
To: =?gb18030?B?Um9iaW4gRGFwcA==?= <rdapp.gcc@gmail.com>,
=?gb18030?B?RGVtaW4gSGFu?= <demin.han@starfivetech.com>,
=?gb18030?B?Z2NjLXBhdGNoZXM=?= <gcc-patches@gcc.gnu.org>
Cc: =?gb18030?B?cmRhcHAuZ2Nj?= <rdapp.gcc@gmail.com>,
=?gb18030?B?a2l0by5jaGVuZw==?= <kito.cheng@gmail.com>,
=?gb18030?B?TGksIFBhbjI=?= <pan2.li@intel.com>,
=?gb18030?B?amVmZnJleWFsYXc=?= <jeffreyalaw@gmail.com>
Subject: Re: [PATCH 1/5] RISC-V: Remove float vector eqne pattern
Date: Thu, 16 May 2024 10:01:40 +0800 [thread overview]
Message-ID: <tencent_4E7CFD325B4AF6481F05E9CA@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 289 bytes --]
Would you minding sending this patch again£¿
I can not find the patch now.
----------Reply to Message----------
On Thu, May 16, 2024 03:48 AM Robin Dapp<rdapp.gcc@gmail.com> wrote:
Hi Demin,
are you still going to continue with this?
Regards
Robin
next reply other threads:[~2024-05-16 2:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 2:01 =?gb18030?B?1tO+09Xc?= [this message]
2024-05-16 2:17 ` Demin Han
-- strict thread matches above, loose matches on Subject: below --
2024-03-01 6:27 [PATCH 0/5] RISC-V: Support vf and vx for autovec comparison of demin.han
2024-03-01 6:27 ` [PATCH 1/5] RISC-V: Remove float vector eqne pattern demin.han
2024-03-01 7:23 ` 钟居哲
2024-03-01 8:12 ` Demin Han
2024-03-01 14:53 ` [PATCH " Robin Dapp
2024-05-15 19:48 ` Robin Dapp
2024-05-16 1:54 ` Demin Han
2024-05-16 19:21 ` Robin Dapp
2024-06-08 20:48 ` Jeff Law
2024-06-10 7:33 ` Robin Dapp
2024-06-10 13:49 ` Jeff Law
2024-06-10 14:52 ` Li, Pan2
2024-06-10 16:30 ` Jeff Law
2024-06-10 16:16 ` Demin Han
2024-06-10 16:23 ` Jeff Law
2024-06-08 20:51 ` Jeff Law
2024-06-08 20:50 ` Jeff Law
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=tencent_4E7CFD325B4AF6481F05E9CA@qq.com \
--to=juzhe.zhong@rivai.ai \
--cc=demin.han@starfivetech.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=pan2.li@intel.com \
--cc=rdapp.gcc@gmail.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).