public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Lehua Ding <lhtin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-4680] RISC-V: Fix failed testcase when use -cmodel=medany Date: Tue, 17 Oct 2023 10:01:05 +0000 (GMT) [thread overview] Message-ID: <20231017100105.176153858D33@sourceware.org> (raw) https://gcc.gnu.org/g:5bb79a427adb57d4a55690f29d4f49e42d68c2a5 commit r14-4680-g5bb79a427adb57d4a55690f29d4f49e42d68c2a5 Author: Lehua Ding <lehua.ding@rivai.ai> Date: Tue Oct 17 17:48:25 2023 +0800 RISC-V: Fix failed testcase when use -cmodel=medany This little path fix a failed testcase when use -cmodel=medany. gcc/testsuite/ChangeLog: * gcc.target/riscv/rvv/base/cpymem-1.c: Split check. Diff: --- gcc/testsuite/gcc.target/riscv/rvv/base/cpymem-1.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.target/riscv/rvv/base/cpymem-1.c b/gcc/testsuite/gcc.target/riscv/rvv/base/cpymem-1.c index 9bb4904e8e9e..549d66481048 100644 --- a/gcc/testsuite/gcc.target/riscv/rvv/base/cpymem-1.c +++ b/gcc/testsuite/gcc.target/riscv/rvv/base/cpymem-1.c @@ -50,7 +50,7 @@ void f2 (__INT32_TYPE__* a, __INT32_TYPE__* b, int l) Use extern here so that we get a known alignment, lest DATA_ALIGNMENT force us to make the scan pattern accomodate code for different alignments depending on word size. -** f3: +** f3: { target { any-opts "-mcmodel=medlow" } } ** lui\s+[ta][0-7],%hi\(a_a\) ** lui\s+[ta][0-7],%hi\(a_b\) ** addi\s+a4,[ta][0-7],%lo\(a_b\) @@ -61,6 +61,16 @@ void f2 (__INT32_TYPE__* a, __INT32_TYPE__* b, int l) ** ret */ +/* +** f3: { target { any-opts "-mcmodel=medany" } } +** lla\s+[ta][0-7],a_b +** vsetivli\s+zero,16,e32,m4,ta,ma +** vle32.v\s+v\d+,0\([ta][0-7]\) +** lla\s+[ta][0-7],a_a +** vse32\.v\s+v\d+,0\([ta][0-7]\) +** ret +*/ + extern struct { __INT32_TYPE__ a[16]; } a_a, a_b; void f3 ()
reply other threads:[~2023-10-17 10:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231017100105.176153858D33@sourceware.org \ --to=lhtin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).