From: "Li Xu" <xuli1@eswincomputing.com>
To: xuli1 <xuli1@eswincomputing.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>,
juzhe.zhong <juzhe.zhong@rivai.ai>
Subject: Re: Re: [PATCH] RISCV: Fix PR111074 [GCC13 BUG]
Date: Tue, 22 Aug 2023 15:28:42 +0800 [thread overview]
Message-ID: <202308221528421084563@eswincomputing.com> (raw)
In-Reply-To: <202308221042417922561@eswincomputing.com>
Committed, thanks all.
--------------
Li Xu
>The test case is too complicated and I can't simplify it, so no test case is added.
>
>--------------
>Li Xu
>>From: xuli <xuli1@eswincomputing.com>
>>
>>This patch fixes this issue happens on GCC-13.
>>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111074
>>
>>This patch should be backported to GCC-13.
>>GCC-14 has rewritten propagate_avl function, so there is no issue.
>>
>>PR target/111074
>>
>>gcc/ChangeLog:
>>
>> * config/riscv/riscv-vsetvl.cc (extract_single_source): Fix bug.
>>---
>> gcc/config/riscv/riscv-vsetvl.cc | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>>diff --git a/gcc/config/riscv/riscv-vsetvl.cc b/gcc/config/riscv/riscv-vsetvl.cc
>>index 789eb04b78d..bd45cb97e63 100644
>>--- a/gcc/config/riscv/riscv-vsetvl.cc
>>+++ b/gcc/config/riscv/riscv-vsetvl.cc
>>@@ -1183,6 +1183,9 @@ extract_single_source (set_info *set)
>> return nullptr;
>> hash_set<set_info *> sets = get_all_sets (set, true, false, true);
>>
>>+ if (sets.is_empty ())
>>+ return nullptr;
>>+
>> insn_info *first_insn = (*sets.begin ())->insn ();
>> if (first_insn->is_artificial ())
>> return nullptr;
>>--
>>2.17.1
prev parent reply other threads:[~2023-08-22 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 2:29 Li Xu
2023-08-22 2:40 ` juzhe.zhong
2023-08-22 2:42 ` Li Xu
2023-08-22 2:44 ` juzhe.zhong
2023-08-22 7:28 ` Li Xu [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=202308221528421084563@eswincomputing.com \
--to=xuli1@eswincomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
/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).