public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kito Cheng <kito@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5429] RISC-V: Reorder VSETVL pass location Date: Fri, 27 Jan 2023 09:40:14 +0000 (GMT) [thread overview] Message-ID: <20230127094014.386123858D20@sourceware.org> (raw) https://gcc.gnu.org/g:5aa486e7740a0bc83168d806806d1149e6e90310 commit r13-5429-g5aa486e7740a0bc83168d806806d1149e6e90310 Author: Ju-Zhe Zhong <juzhe.zhong@rivai.ai> Date: Wed Jan 18 11:03:47 2023 +0800 RISC-V: Reorder VSETVL pass location Insert before dce means we don't invoke DCE by this pass itself, and also we can leverage the effort of BB reorder. gcc/ChangeLog: * config/riscv/riscv-passes.def (INSERT_PASS_BEFORE): Reorder VSETVL pass. Diff: --- gcc/config/riscv/riscv-passes.def | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/config/riscv/riscv-passes.def b/gcc/config/riscv/riscv-passes.def index e68de681943..4084122cf0a 100644 --- a/gcc/config/riscv/riscv-passes.def +++ b/gcc/config/riscv/riscv-passes.def @@ -18,4 +18,4 @@ <http://www.gnu.org/licenses/>. */ INSERT_PASS_AFTER (pass_rtl_store_motion, 1, pass_shorten_memrefs); -INSERT_PASS_BEFORE (pass_sched2, 1, pass_vsetvl); +INSERT_PASS_BEFORE (pass_fast_rtl_dce, 1, pass_vsetvl);
reply other threads:[~2023-01-27 9:40 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230127094014.386123858D20@sourceware.org \ --to=kito@gcc.gnu.org \ --cc=gcc-cvs@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).