public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kito at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108185] [RISC-V]RVV assemble not set vsetvli correct.
Date: Thu, 29 Dec 2022 09:51:04 +0000 [thread overview]
Message-ID: <bug-108185-4-0iSTrysRuX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108185-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108185
Kito Cheng <kito at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kito at gcc dot gnu.org
--- Comment #2 from Kito Cheng <kito at gcc dot gnu.org> ---
It seems right to me?
```
$ riscv64-unknown-elf-gcc pr108185.c -march=rv64gcv -mabi=lp64d -O3 -S -o -
.file "pr108185.c"
.option nopic
.attribute arch,
"rv64i2p0_m2p0_a2p0_f2p0_d2p0_c2p0_v1p0_zve32f1p0_zve32x1p0_zve64d1p0_zve64f1p0_zve64x1p0_zvl128b1p0_zvl32b1p0_zvl64b1p0"
.attribute unaligned_access, 0
.attribute stack_align, 16
.text
.align 1
.globl foo5_3
.type foo5_3, @function
foo5_3:
csrr t0,vlenb
slli t1,t0,1
csrr a5,vlenb
sub sp,sp,t1
slli a3,a5,1
add a3,a3,sp
vl1re8.v v25,0(a0) # Load value from *(vint8m1_t*)in
sub a5,a3,a5
vs1r.v v25,0(a1) # Store value to *(vint8m1_t*)out
vs1r.v v25,0(a5) # Store value to stack, although it's
unused.
addi a4,a1,800
csrr t0,vlenb
slli t1,t0,1
vsetvli a5,zero,e8,m1,ta,ma # Right vsetvli for vsm.v
vsm.v v25,0(a4)
add sp,sp,t1
jr ra
.size foo5_3, .-foo5_3
.ident "GCC: (g44b22ab81cf) 13.0.0 20221229 (experimental)"
```
next prev parent reply other threads:[~2022-12-29 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 3:55 [Bug target/108185] New: " jiawei at iscas dot ac.cn
2022-12-20 3:58 ` [Bug target/108185] " jiawei at iscas dot ac.cn
2022-12-29 9:51 ` kito at gcc dot gnu.org [this message]
2023-01-03 1:54 ` jiawei at iscas dot ac.cn
2023-01-03 2:32 ` [Bug target/108185] [RISC-V] Sub-optimal code-gen for vsetvli: redundant stack store kito at gcc dot gnu.org
2023-02-03 3:05 ` juzhe.zhong at rivai dot ai
2023-03-07 13:45 ` cvs-commit at gcc dot gnu.org
2023-03-08 1:11 ` kito at gcc dot gnu.org
2023-03-23 8:40 ` cvs-commit at gcc dot gnu.org
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=bug-108185-4-0iSTrysRuX@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).