From: Robin Dapp <rdapp.gcc@gmail.com>
To: "juzhe.zhong" <juzhe.zhong@rivai.ai>, Kito Cheng <kito.cheng@sifive.com>
Cc: rdapp.gcc@gmail.com, gcc-patches <gcc-patches@gcc.gnu.org>,
jeffreyalaw <jeffreyalaw@gmail.com>,
"kito.cheng" <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>,
palmer <palmer@rivosinc.com>
Subject: Re: [PATCH] RISC-V: Enable COND_LEN_FMA auto-vectorization
Date: Thu, 13 Jul 2023 17:25:23 +0200 [thread overview]
Message-ID: <3c25fe13-b8d6-e9b0-de13-e25e650a379b@gmail.com> (raw)
In-Reply-To: <7E3872FEA7869C1F+05F987C9-E32C-4BE0-9BFC-9BC2C3B59134@rivai.ai>
> Is COND _LEN FMA ok for trunk? I can commit it without changing
> scatter store testcase fix.
>
> It makes no sense block cond Len fma support. The middle end support
> has already been merged.
Then just add a TODO or so that says e.g. "For some reason we exceed
the default code model's +-2 GiB limits. We should investigate why and
add a proper description here. For now just make sure the test case
compiles properly".
Regards
Robin
next prev parent reply other threads:[~2023-07-13 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 11:32 Juzhe-Zhong
2023-07-13 11:40 ` Robin Dapp
2023-07-13 11:44 ` juzhe.zhong
2023-07-13 11:49 ` juzhe.zhong
2023-07-13 14:39 ` Kito Cheng
2023-07-13 14:40 ` 钟居哲
[not found] ` <7E3872FEA7869C1F+05F987C9-E32C-4BE0-9BFC-9BC2C3B59134@rivai.ai>
2023-07-13 15:25 ` Robin Dapp [this message]
2023-07-13 22:17 ` 钟居哲
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=3c25fe13-b8d6-e9b0-de13-e25e650a379b@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=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.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).