public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lehua.ding at rivai dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111725] New: Missed one vsetvl
Date: Sun, 08 Oct 2023 08:06:46 +0000	[thread overview]
Message-ID: <bug-111725-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111725

            Bug ID: 111725
           Summary: Missed one vsetvl
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: lehua.ding at rivai dot ai
  Target Milestone: ---

online: https://godbolt.org/z/br456cPs8
C Code (compiler option: -march=rv32gcv -mabi=ilp32d -S -fno-schedule-insns
-fno-schedule-insns2  -fno-tree-vectorize -frename-registers -O2):

#include "riscv_vector.h"

float f (int8_t * restrict in, int8_t * restrict out, int n, int m, unsigned
cond, size_t vl, float scalar)
{
  vbool64_t mask = *(vbool64_t*) (in + 1000000);

  for (size_t i = 0; i < n; i++)
    {
      vfloat32mf2_t v = __riscv_vle32_v_f32mf2 ((float *)(in + i + 200),
__riscv_vsetvlmax_e32mf2 ());
      __riscv_vse32_v_f32mf2 ((float *)(out + i + 200), v,
__riscv_vsetvlmax_e32mf2 ());

      vfloat32mf2_t v2 = __riscv_vle32_v_f32mf2_tumu (mask, v, (float *)(in + i
+ 300), __riscv_vsetvlmax_e32mf2 ());
      __riscv_vse32_v_f32mf2_m (mask, (float *)(out + i + 300), v2,
__riscv_vsetvlmax_e32mf2 ());
    }

  vfloat32m1_t v = *(vfloat32m1_t*)(in + 300000);
  for (size_t i = 0; i < n; i++)
    {
      v = __riscv_vfmv_s_f_f32m1_tu (v, (scalar + i), 3);
    }
  v = __riscv_vfadd_vv_f32m1 (v,v, 3);
  return __riscv_vfmv_f_s_f32m1_f32 (v);
}

Assembly Code:

f:
        li      a5,999424
        addi    t0,a5,576
        add     t1,a0,t0
        vsetvli a4,zero,e32,mf2,tu,mu
        vlm.v   v0,0(t1)
        beq     a2,zero,.L2
        addi    t5,a0,200
        addi    t6,a1,300
        addi    a6,a2,200
        add     t3,a0,a6
.L3:
        vle32.v v1,0(t5)
        addi    a3,t6,-100
        vse32.v v1,0(a3)
        addi    t4,t5,100
        vle32.v v1,0(t4),v0.t
        vse32.v v1,0(t6),v0.t
        addi    t5,t5,1
        addi    t6,t6,1
        bne     t5,t3,.L3
        li      a5,299008
        addi    t0,a5,992
        add     t1,a0,t0
        vl1re32.v       v2,0(t1)
        li      a4,0
.L6:
        fcvt.s.wu       fa5,a4
        fadd.s  ft0,fa5,fa0
        vfmv.s.f        v2,ft0
        addi    a4,a4,1
        bne     a4,a2,.L6
        vfadd.vv        v3,v2,v2 # Miss vsetivli zero,3,e32,m1,ta,ma
        vfmv.f.s        fa0,v3
        ret
.L2:
        li      t2,299008
        addi    a1,t2,992
        add     a0,a0,a1
        vl1re32.v       v2,0(a0)
        vsetivli        zero,3,e32,m1,ta,ma
        vfadd.vv        v3,v2,v2
        vfmv.f.s        fa0,v3
        ret

             reply	other threads:[~2023-10-08  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-08  8:06 lehua.ding at rivai dot ai [this message]
2023-10-20  3:57 ` [Bug target/111725] Missed one vsetivli insn cvs-commit at gcc dot gnu.org
2023-10-24  3:01 ` lehua.ding at rivai dot ai
2023-10-25  6:20 ` lehua.ding at rivai dot ai

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-111725-4@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).