public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114809] [RISC-V RVV] Counting elements might be simpler Date: Mon, 22 Apr 2024 22:23:52 +0000 [thread overview] Message-ID: <bug-114809-4-XbBpREdZqy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114809-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114809 JuzheZhong <juzhe.zhong at rivai dot ai> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juzhe.zhong at rivai dot ai --- Comment #3 from JuzheZhong <juzhe.zhong at rivai dot ai> --- For missed peephole optimization, I already noticed it long time ago, and I have filed PR: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113014 Such issue will gone after Richard Standiford @arm merged late-combine PASS in GCC 15. Also, GCC support dynamic LMUL optimization with -mrvv-max-lmul=dynamic: https://godbolt.org/z/646nYoKbv ASM: count_chars(char const*, unsigned long, char): beq a1,zero,.L4 vsetvli a4,zero,e8,m1,ta,ma vmv.v.x v1,a2 vsetvli zero,zero,e64,m8,ta,ma vmv.v.i v8,0 .L3: vsetvli a5,a1,e8,m1,ta,ma vle8.v v0,0(a0) sub a1,a1,a5 add a0,a0,a5 vmseq.vv v0,v0,v1 vsetvli zero,zero,e64,m8,tu,mu vadd.vi v8,v8,1,v0.t bne a1,zero,.L3 vsetvli a5,zero,e64,m8,ta,ma li a4,0 vmv.s.x v1,a4 vredsum.vs v8,v8,v1 vmv.x.s a0,v8 ret .L4: li a0,0 ret GCC picks LMUL = 8, since it doesn't cause additional register spillings according to the program register pressure.
prev parent reply other threads:[~2024-04-22 22:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-22 17:10 [Bug target/114809] New: " wojciech_mula at poczta dot onet.pl 2024-04-22 20:24 ` [Bug target/114809] " palmer at gcc dot gnu.org 2024-04-22 21:11 ` andrew at sifive dot com 2024-04-22 21:59 ` pinskia at gcc dot gnu.org 2024-04-22 22:23 ` juzhe.zhong at rivai dot ai [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=bug-114809-4-XbBpREdZqy@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: 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).