From: Jeff Law <jeffreyalaw@gmail.com>
To: Patrick O'Neill <patrick@rivosinc.com>, gcc-patches@gcc.gnu.org
Cc: rdapp.gcc@gmail.com, juzhe.zhong@rivai.ai
Subject: Re: [PATCH] RISC-V: Add -fno-vect-cost-model to pr112773 testcase
Date: Fri, 15 Dec 2023 14:47:59 -0700 [thread overview]
Message-ID: <9e63ad78-e34b-4107-8bb2-f3711efe96aa@gmail.com> (raw)
In-Reply-To: <20231214213201.180346-1-patrick@rivosinc.com>
On 12/14/23 14:32, Patrick O'Neill wrote:
> The testcase for pr112773 started passing after r14-6472-g8501edba91e
> which was before the actual fix. This patch adds -fno-vect-cost-model
> which prevents the testcase from passing due to the vls change.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/autovec/partial/pr112773.c: Add
> -fno-vect-cost-model.
>
> Signed-off-by: Patrick O'Neill <patrick@rivosinc.com>
I've pushed this to the trunk.
jeff
prev parent reply other threads:[~2023-12-15 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 21:32 Patrick O'Neill
2023-12-14 22:07 ` 钟居哲
2023-12-15 21:47 ` Jeff Law [this message]
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=9e63ad78-e34b-4107-8bb2-f3711efe96aa@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=patrick@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).