public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Dapp <rdapp.gcc@gmail.com>
To: 钟居哲 <juzhe.zhong@rivai.ai>, "Jeff Law" <jeffreyalaw@gmail.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	palmer <palmer@dabbelt.com>, "kito.cheng" <kito.cheng@gmail.com>
Cc: rdapp.gcc@gmail.com
Subject: Re: [PATCH] RISC-V: Add autovec FP unary operations.
Date: Thu, 15 Jun 2023 10:24:34 +0200	[thread overview]
Message-ID: <da42d875-4683-9e36-9baa-75457cb3d78d@gmail.com> (raw)
In-Reply-To: <C082D80E441B7DA6+2023061505153418390417@rivai.ai>

Hi Juzhe,

I like the iterator solution better,  I added it to the
binops V2 patch with a comment and will post it in a while.
Also realized there is already a testcase and the "enabled"
attribute is set properly now but I hadn't rebased to the
current master branch in a while...

Btw. I'm currently running the testsuite with rv64gcv_zfhmin
default march and see some additional FAILs.  Will report back.

Regards
 Robin

  reply	other threads:[~2023-06-15  8:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 15:31 Robin Dapp
2023-06-14 19:43 ` Jeff Law
2023-06-14 21:15   ` 钟居哲
2023-06-15  8:24     ` Robin Dapp [this message]
2023-06-15 14:33       ` Robin Dapp
2023-06-17  2:17     ` Jeff Law
     [not found]   ` <2023061505153418390417@rivai.ai>
2023-06-14 21:27     ` 钟居哲
2023-06-15  2:31 ` juzhe.zhong
2023-06-15 15:12 ` [PATCH v2] " Robin Dapp
2023-06-15 16:46   ` Michael Collison
2023-06-15 17:05   ` 钟居哲
2023-06-16 13:32   ` [PATCH v3] " Robin Dapp
     [not found]   ` <3D189BAB610F6C4E+160C6AB4-2BD8-4A9A-A1EC-5081D07AE627@rivai.ai>
2023-06-17  2:18     ` 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=da42d875-4683-9e36-9baa-75457cb3d78d@gmail.com \
    --to=rdapp.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=juzhe.zhong@rivai.ai \
    --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).