public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mumuxi_ll at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/111621] New: [RISC-V] Bad register allocation in vadd.vi may cause operational error
Date: Thu, 28 Sep 2023 07:36:26 +0000	[thread overview]
Message-ID: <bug-111621-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111621
           Summary: [RISC-V] Bad register allocation in vadd.vi may cause
                    operational error
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mumuxi_ll at outlook dot com
  Target Milestone: ---

Hi;

My source code can be fond at https://godbolt.org/z/8v9Wxx9Yf.

The porblem is that when compiling with -O2/-O3, vadd.vi will allocate a
different  register for vd compared to vs2, then the actual operation will only
update the first data in vd instead of all. In cases such as -O0, vadd.vi will
allocate the same registers to vd and vs2, and all vd values will be refreshed
after execution.

Thanks!

             reply	other threads:[~2023-09-28  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28  7:36 mumuxi_ll at outlook dot com [this message]
2023-09-28 20:34 ` [Bug middle-end/111621] " pinskia at gcc dot gnu.org
2023-10-08  4:11 ` mumuxi_ll at outlook dot com
2023-10-09  1:12 ` juzhe.zhong 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-111621-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).