From: Robin Dapp <rdapp.gcc@gmail.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: rdapp.gcc@gmail.com, "kito.cheng" <kito.cheng@gmail.com>,
"Kito.cheng" <kito.cheng@sifive.com>,
jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: [PATCH V4] RISC-V: Support Dynamic LMUL Cost model
Date: Tue, 12 Sep 2023 11:31:34 +0200 [thread overview]
Message-ID: <a4e22956-fc2a-00f0-96ed-7db148a16c0f@gmail.com> (raw)
In-Reply-To: <6710B99B5C7487DA+2023091217250873108440@rivai.ai>
> 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:31 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 [this message]
2023-09-12 9:36 ` juzhe.zhong
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=a4e22956-fc2a-00f0-96ed-7db148a16c0f@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 \
/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).