public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xuli1 at eswincomputing dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111412] New: [release/gcc13 bug]RISC-V:ICE in phase 6 of vsetvl pass Date: Thu, 14 Sep 2023 09:05:37 +0000 [thread overview] Message-ID: <bug-111412-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111412 Bug ID: 111412 Summary: [release/gcc13 bug]RISC-V:ICE in phase 6 of vsetvl pass Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: xuli1 at eswincomputing dot com Target Milestone: --- Created attachment 55899 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55899&action=edit testcase Compile the code using -march=rv64gcv -mabi=lp64d -O2: test: beq a0,zero,.L2 lui a5,%hi(.LC0) flw fa4,%lo(.LC0)(a5) fmv.s.x fa5,zero li a3,1 vfmv.v.f v1,fa4 --> The vsetvl instruction was not set before this,causing Illegal instruction (core dumped) .L5: slli a5,a3,32 srli a5,a5,32 vsetvli a5,a5,e32,m8,ta,mu beq a5,zero,.L3 mv a4,a3 ..... Solution: vsetvl pass has been refactored in gcc14, and the optimization process is more reasonable than gcc13. This problem does not exist in gcc14. Phase 6 of gcc13 is an optimization patch. Due to lack of consideration, there will be some hidden bugs, so we decided to remove phase 6. Although the generated code will be redundant,the program is correct.
next reply other threads:[~2023-09-14 9:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-14 9:05 xuli1 at eswincomputing dot com [this message] 2023-09-18 7:14 ` [Bug target/111412] RISC-V:ICE " cvs-commit at gcc dot gnu.org 2023-09-18 8:13 ` kito 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-111412-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: 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).