From: Andreas Schwab <schwab@linux-m68k.org>
To: juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org, kito.cheng@gmail.com,
kito.cheng@sifive.com, palmer@dabbelt.com, palmer@rivosinc.com,
jeffreyalaw@gmail.com, rdapp.gcc@gmail.com, pan2.li@intel.com
Subject: Re: [PATCH V2] RISC-V: Rework Phase 5 && Phase 6 of VSETVL PASS
Date: Fri, 16 Jun 2023 12:55:09 +0200 [thread overview]
Message-ID: <87y1kjr81e.fsf@igel.home> (raw)
In-Reply-To: <20230609104105.9100-1-juzhe.zhong@rivai.ai> (juzhe zhong's message of "Fri, 9 Jun 2023 18:41:05 +0800")
Why didn't you test that??
../../gcc/config/riscv/riscv-vsetvl.cc: In member function 'bool pass_vsetvl::global_eliminate_vsetvl_insn(const rtl_ssa::bb_info*) const':
../../gcc/config/riscv/riscv-vsetvl.cc:4354:3: error: 'vsetvl_rinsn' may be used uninitialized [-Werror=maybe-uninitialized]
4354 | if (!vsetvl_rinsn)
| ^~
../../gcc/config/riscv/riscv-vsetvl.cc:4343:13: note: 'vsetvl_rinsn' was declared here
4343 | rtx_insn *vsetvl_rinsn;
| ^~~~~~~~~~~~
cc1plus: all warnings being treated as errors
make[3]: *** [../../gcc/config/riscv/t-riscv:66: riscv-vsetvl.o] Error 1
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-06-16 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 10:41 juzhe.zhong
2023-06-09 10:45 ` Kito Cheng
2023-06-09 10:49 ` juzhe.zhong
2023-06-09 14:33 ` Jeff Law
2023-06-09 14:46 ` 钟居哲
2023-06-09 14:58 ` 钟居哲
2023-06-09 15:09 ` Jeff Law
2023-06-09 22:52 ` 钟居哲
2023-06-12 19:02 ` Richard Sandiford
2023-06-16 10:55 ` Andreas Schwab [this message]
2023-06-16 11:39 ` Li, Pan2
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=87y1kjr81e.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=pan2.li@intel.com \
--cc=rdapp.gcc@gmail.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).