public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111600] [14 Regression] RISC-V bootstrap time regression Date: Mon, 06 Nov 2023 22:07:44 +0000 [thread overview] Message-ID: <bug-111600-4-MlrasAOegd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111600-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600 --- Comment #32 from JuzheZhong <juzhe.zhong at rivai dot ai> --- 26% time reduction seems not enough. Maybe we still need to optimize MD patterns to fix this issue ? But I have no idea to optimize it since I already tried my best to reduce them. According to RVV intrinsic doc: https://github.com/riscv-non-isa/rvv-intrinsic-doc we have these 6 types variant intrinsics: __vop __vop_tu __vop_mu __vop_tum __vop_tumu __vop_m I have fused them into same pattern (which makes the pattern so complicated) to avoid explosion of MD patterns (otherwise, it will explode 6 times if we dedicate each type intrinsic one MD pattern). But seems it's still an issue. And I have no idea how to reduce them.
next prev parent reply other threads:[~2023-11-06 22:07 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-26 13:35 [Bug target/111600] New: [14.0 regression] " schwab@linux-m68k.org 2023-09-26 17:41 ` [Bug target/111600] " pinskia at gcc dot gnu.org 2023-09-27 7:36 ` [Bug target/111600] [14 Regression] " rguenth at gcc dot gnu.org 2023-09-27 7:47 ` schwab@linux-m68k.org 2023-09-27 7:50 ` schwab@linux-m68k.org 2023-09-27 8:00 ` rguenth at gcc dot gnu.org 2023-09-27 13:36 ` schwab@linux-m68k.org 2023-09-27 17:50 ` palmer at gcc dot gnu.org 2023-09-27 18:22 ` schwab@linux-m68k.org 2023-09-28 8:06 ` schwab@linux-m68k.org 2023-09-28 9:47 ` rguenth at gcc dot gnu.org 2023-09-28 13:14 ` cvs-commit at gcc dot gnu.org 2023-10-02 15:03 ` rdapp at gcc dot gnu.org 2023-10-02 15:28 ` kito at gcc dot gnu.org 2023-10-03 15:26 ` kito at gcc dot gnu.org 2023-10-04 6:46 ` rguenth at gcc dot gnu.org 2023-10-04 8:17 ` rdapp at gcc dot gnu.org 2023-10-04 9:07 ` rguenther at suse dot de 2023-10-04 12:50 ` rdapp at gcc dot gnu.org 2023-10-04 13:13 ` rguenth at gcc dot gnu.org 2023-10-04 13:21 ` rdapp at gcc dot gnu.org 2023-10-04 13:56 ` rguenth at gcc dot gnu.org 2023-10-04 14:38 ` rdapp at gcc dot gnu.org 2023-10-12 11:50 ` rdapp at gcc dot gnu.org 2023-10-13 1:39 ` juzhe.zhong at rivai dot ai 2023-10-13 7:28 ` rdapp at gcc dot gnu.org 2023-10-13 8:01 ` rdapp at gcc dot gnu.org 2023-10-13 8:04 ` rguenther at suse dot de 2023-10-31 12:35 ` cvs-commit at gcc dot gnu.org 2023-11-01 2:24 ` juzhe.zhong at rivai dot ai 2023-11-02 9:31 ` rdapp at gcc dot gnu.org 2023-11-06 18:15 ` schwab@linux-m68k.org 2023-11-06 22:07 ` juzhe.zhong at rivai dot ai [this message] 2024-03-04 4:31 ` law at gcc dot gnu.org 2024-04-30 8:26 ` [Bug target/111600] [14/15 " cvs-commit at gcc dot gnu.org 2024-05-07 7:42 ` rguenth 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-111600-4-MlrasAOegd@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).