public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/113495] RISC-V: Time and memory awful consumption of SPEC2017 wrf benchmark Date: Fri, 19 Jan 2024 10:03:59 +0000 [thread overview] Message-ID: <bug-113495-4-TWFAtdYXoJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113495-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495 --- Comment #24 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Robin Dapp <rdapp@gcc.gnu.org>: https://gcc.gnu.org/g:01260a823073675e13dd1fc85cf2657a5396adf2 commit r14-8282-g01260a823073675e13dd1fc85cf2657a5396adf2 Author: Juzhe-Zhong <juzhe.zhong@rivai.ai> Date: Fri Jan 19 16:34:25 2024 +0800 RISC-V: Fix RVV_VLMAX This patch fixes memory hog found in SPEC2017 wrf benchmark which caused by RVV_VLMAX since RVV_VLMAX generate brand new rtx by gen_rtx_REG (Pmode, X0_REGNUM) every time we call RVV_VLMAX, that is, we are always generating garbage and redundant (reg:DI 0 zero) rtx. After this patch fix, the memory hog is gone. Time variable usr sys wall GGC machine dep reorg : 1.99 ( 9%) 0.35 ( 56%) 2.33 ( 10%) 939M ( 80%) [Before this patch] machine dep reorg : 1.71 ( 6%) 0.16 ( 27%) 3.77 ( 6%) 659k ( 0%) [After this patch] Time variable usr sys wall GGC machine dep reorg : 75.93 ( 18%) 14.23 ( 88%) 90.15 ( 21%) 33383M ( 95%) [Before this patch] machine dep reorg : 56.00 ( 14%) 7.92 ( 77%) 63.93 ( 15%) 4361k ( 0%) [After this patch] Test is running. Ok for trunk if I passed the test with no regresion ? PR target/113495 gcc/ChangeLog: * config/riscv/riscv-protos.h (RVV_VLMAX): Change to regno_reg_rtx[X0_REGNUM]. (RVV_VUNDEF): Ditto. * config/riscv/riscv-vsetvl.cc: Add timevar.
next prev parent reply other threads:[~2024-01-19 10:04 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-19 1:22 [Bug c/113495] New: " juzhe.zhong at rivai dot ai 2024-01-19 1:36 ` [Bug tree-optimization/113495] " juzhe.zhong at rivai dot ai 2024-01-19 1:38 ` juzhe.zhong at rivai dot ai 2024-01-19 1:48 ` juzhe.zhong at rivai dot ai 2024-01-19 1:52 ` juzhe.zhong at rivai dot ai 2024-01-19 1:55 ` [Bug rtl-optimization/113495] " pinskia at gcc dot gnu.org 2024-01-19 1:56 ` juzhe.zhong at rivai dot ai 2024-01-19 3:08 ` patrick at rivosinc dot com 2024-01-19 3:12 ` pinskia at gcc dot gnu.org 2024-01-19 3:14 ` pinskia at gcc dot gnu.org 2024-01-19 3:33 ` juzhe.zhong at rivai dot ai 2024-01-19 3:34 ` juzhe.zhong at rivai dot ai 2024-01-19 3:44 ` juzhe.zhong at rivai dot ai 2024-01-19 3:46 ` juzhe.zhong at rivai dot ai 2024-01-19 3:52 ` juzhe.zhong at rivai dot ai 2024-01-19 3:56 ` pinskia at gcc dot gnu.org 2024-01-19 3:58 ` juzhe.zhong at rivai dot ai 2024-01-19 4:00 ` juzhe.zhong at rivai dot ai 2024-01-19 8:23 ` juzhe.zhong at rivai dot ai 2024-01-19 8:41 ` juzhe.zhong at rivai dot ai 2024-01-19 9:23 ` rguenth at gcc dot gnu.org 2024-01-19 9:24 ` rguenth at gcc dot gnu.org 2024-01-19 9:28 ` juzhe.zhong at rivai dot ai 2024-01-19 9:35 ` kito at gcc dot gnu.org 2024-01-19 10:03 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-19 10:05 ` juzhe.zhong at rivai dot ai 2024-01-19 10:22 ` rguenther at suse dot de 2024-01-22 11:42 ` rdapp at gcc dot gnu.org 2024-01-22 11:51 ` juzhe.zhong at rivai dot ai 2024-01-22 12:00 ` rguenth at gcc dot gnu.org 2024-01-22 13:21 ` juzhe.zhong at rivai dot ai 2024-01-22 15:04 ` juzhe.zhong at rivai dot ai 2024-01-24 0:30 ` cvs-commit at gcc dot gnu.org 2024-01-31 0:29 ` cvs-commit at gcc dot gnu.org 2024-01-31 1:25 ` 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-113495-4-TWFAtdYXoJ@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).