From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: "Robin Dapp" <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "Robin Dapp" <rdapp.gcc@gmail.com>,
kito.cheng <kito.cheng@gmail.com>,
Kito.cheng <kito.cheng@sifive.com>,
jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: Re: [PATCH V4] RISC-V: Support Dynamic LMUL Cost model
Date: Tue, 12 Sep 2023 17:36:41 +0800 [thread overview]
Message-ID: <60C0CC476BFCFF53+2023091217364091739043@rivai.ai> (raw)
In-Reply-To: <a4e22956-fc2a-00f0-96ed-7db148a16c0f@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
This is first version of dynamic LMUL.
I didn't test it with full GCC testsuite.
My plan is to first pass all GCC testsuite (including vect.exp) with default LMUL = M1.
Then enable dynamic LMUL to test it.
Maybe we could tolerate this ICE issue for now. Then we can test it with full GCC testsuite (I belive we can reproduce with some case in GCC testsuite in the future).
Is that reasonable ? If yes, I will fix all your comments and send V5.
juzhe.zhong@rivai.ai
From: Robin Dapp
Date: 2023-09-12 17:31
To: juzhe.zhong@rivai.ai; gcc-patches
CC: rdapp.gcc; kito.cheng; Kito.cheng; jeffreyalaw
Subject: Re: [PATCH V4] RISC-V: Support Dynamic LMUL Cost model
> Is calculix big ?
It's 7 nested for loops IIRC and, when unrolling, can get pretty nasty.
I tested with -Ofast -funroll-loops. I think wrf is even larger, maybe I
can run a full comparison test tonight to have good coverage.
> Could you give me the testcase to reproduce it?
OK, I will try to reduce it, will be Fortran, though.
Regards
Robin
next prev parent reply other threads:[~2023-09-12 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 6:49 Juzhe-Zhong
2023-09-12 8:19 ` Robin Dapp
2023-09-12 9:14 ` juzhe.zhong
2023-09-12 9:17 ` Robin Dapp
2023-09-12 9:25 ` juzhe.zhong
2023-09-12 9:31 ` Robin Dapp
2023-09-12 9:36 ` juzhe.zhong [this message]
2023-09-12 10:57 ` Robin Dapp
[not found] ` <2023091217364091739043@rivai.ai>
2023-09-12 9:38 ` juzhe.zhong
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=60C0CC476BFCFF53+2023091217364091739043@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.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).