public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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>,  palmer <palmer@dabbelt.com>,
	 palmer <palmer@rivosinc.com>,
	 jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: Re: [PATCH] RISC-V: Enable COND_LEN_FMA auto-vectorization
Date: Thu, 13 Jul 2023 19:44:56 +0800	[thread overview]
Message-ID: <26E044C7DF261866+2023071319445612164222@rivai.ai> (raw)
In-Reply-To: <65a82d0a-f927-c63a-d283-59a3439b6830@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 745 bytes --]

I have no ideal.

This testcase cause link ICE:
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/scatter_store_run-7.c (test for excess errors)
Excess errors:
scatter_store_run-7.c:(.text.startup+0xc8e): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR1'

only LMUL = M8 will cause such issue.



juzhe.zhong@rivai.ai
 
From: Robin Dapp
Date: 2023-07-13 19:40
To: Juzhe-Zhong; gcc-patches
CC: rdapp.gcc; kito.cheng; kito.cheng; palmer; palmer; jeffreyalaw
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
 

  reply	other threads:[~2023-07-13 11:45 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 [this message]
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
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=26E044C7DF261866+2023071319445612164222@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=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).