public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Dapp <rdapp.gcc@gmail.com>
To: Michael Collison <collison@rivosinc.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	palmer <palmer@dabbelt.com>, Kito Cheng <kito.cheng@gmail.com>,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
	jeffreyalaw <jeffreyalaw@gmail.com>
Cc: rdapp.gcc@gmail.com
Subject: Re: [PATCH v2] RISC-V: Add autovec FP binary operations.
Date: Fri, 16 Jun 2023 14:41:47 +0200	[thread overview]
Message-ID: <ffbcbeaa-6e15-fada-4ae2-7f23ddc67f0f@gmail.com> (raw)
In-Reply-To: <a326f3c3-01f4-8b1c-77a2-e3dd9b1a35fe@rivosinc.com>

> Why do we need '-ffast-math' with the tests?

Normally we would use the COND_ADD to mask out possibly trapping
vector elements and the likes but COND_ADD works with normal
vector masking.  What we currently have is no masking but the
LEN_LOAD/LEN_STORE machinery i.e. length-controlled loops.
There is no LEN_MASK_COND_ADD yet, but Juzhe is working to upstream
it.  Once this is in place we don't need -ffast-math anymore.

Regards
 Robin


  reply	other threads:[~2023-06-16 12:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 15:28 [PATCH] " Robin Dapp
2023-06-15 15:10 ` [PATCH v2] " Robin Dapp
2023-06-15 16:33   ` Michael Collison
2023-06-16 12:41     ` Robin Dapp [this message]
2023-06-16  6:58   ` juzhe.zhong
2023-06-16  7:31     ` Robin Dapp
     [not found] ` <3593152A4AF6C445+E892D494-DF60-4B27-928D-14A269989B2B@rivai.ai>
2023-06-16 13:29   ` [PATCH v3] " Robin Dapp
2023-09-06  9:43     ` Lehua Ding
2023-09-06 13:27       ` Robin Dapp
2023-09-07  3:25         ` Lehua Ding
     [not found]   ` <1609CD82F4EC3898+30AECC2C-6966-43A1-854C-C14F08E5D45B@rivai.ai>
2023-06-17  2:20     ` 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=ffbcbeaa-6e15-fada-4ae2-7f23ddc67f0f@gmail.com \
    --to=rdapp.gcc@gmail.com \
    --cc=collison@rivosinc.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).