From: Kito Cheng <kito.cheng@sifive.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: Robin Dapp <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: Re: [PATCH] RISC-V: Enable COND_LEN_FMA auto-vectorization
Date: Thu, 13 Jul 2023 22:39:26 +0800 [thread overview]
Message-ID: <CALLt3Thy_nnFwfd+DN1_xoMDvBffx11N0E2mR7MLH9yhck88-Q@mail.gmail.com> (raw)
In-Reply-To: <59D9503707DFF6A3+2023071319493989380523@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
I didn’t try on local yet, but it sounds like …the code size might larger
than normal case?
juzhe.zhong@rivai.ai <juzhe.zhong@rivai.ai>於 2023年7月13日 週四，19:50寫道：
> Could you tell me how to add the comment?
> I am not familiar with link/binutils stuff.
>
> ------------------------------
> juzhe.zhong@rivai.ai
>
>
> *From:* Robin Dapp <rdapp.gcc@gmail.com>
> *Date:* 2023-07-13 19:40
> *To:* Juzhe-Zhong <juzhe.zhong@rivai.ai>; gcc-patches
> <gcc-patches@gcc.gnu.org>
> *CC:* rdapp.gcc <rdapp.gcc@gmail.com>; kito.cheng <kito.cheng@gmail.com>;
> kito.cheng <kito.cheng@sifive.com>; palmer <palmer@dabbelt.com>; palmer
> <palmer@rivosinc.com>; jeffreyalaw <jeffreyalaw@gmail.com>
> *Subject:* Re: [PATCH] RISC-V: Enable COND_LEN_FMA auto-vectorization
> Hi Juzhe,
>
> thanks, no complaints from my side apart from one:
>
> > +/* { dg-additional-options "-mcmodel=medany" } */
>
> Please add a comment why we need this.
>
> Regards
> Robin
>
>
>
next prev parent reply other threads:[~2023-07-13 14:39 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 [this message]
2023-07-13 14:40 ` 钟居哲
[not found] ` <7E3872FEA7869C1F+05F987C9-E32C-4BE0-9BFC-9BC2C3B59134@rivai.ai>
2023-07-13 15:25 ` Robin Dapp
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=CALLt3Thy_nnFwfd+DN1_xoMDvBffx11N0E2mR7MLH9yhck88-Q@mail.gmail.com \
--to=kito.cheng@sifive.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 \
--cc=palmer@rivosinc.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).