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/109971] [14 regression] Several powerpc64 vector test cases fail after r14-1242-gf574e2dfae7905 Date: Fri, 26 May 2023 05:28:08 +0000 [thread overview] Message-ID: <bug-109971-4-AkYV0J1ncc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109971-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109971 --- Comment #6 from JuzheZhong <juzhe.zhong at rivai dot ai> --- >> With decrement IV, the optimized IR actually becomes better, it also aligns >>with our discussion here: https://gcc.gnu.org/pipermail/gcc-patches/2023->>April/615629.html (Thanks for the improvement!) Oh, I see. It seems that my patch is overall beneficial to PowerPC? That's what I want since I want my patch can not only help RVV but also other targets. >>It exposes something inefficient at -O2, it seems we can teach cunroll further >>about this kind of new sequence. Ok, we can optimize it for decrement IV in the future. >>If you meant to disable decrement IV on Power (but now actually enable it >>unexpectedly), then probably we can just keep it (not disabling), for Power we >>mainly adopt --param=vect-partial-vector-usage=1, it shouldn't be affected, for >>--param=vect-partial-vector-usage=2, it does generate better code sequence for >>most cases and we can improve the remaining worse one gradually. I am not meant to disable decrement IV on Power. Actually, I really hope Power can reuse the flow that I build for RVV. It makes things more meaningful. If it works for power and it seems to improve power codegen in most cases, I'd like to see power enable it by default. Then we can optimize it togther. Thanks a lot for your information.
next prev parent reply other threads:[~2023-05-26 5:28 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-25 22:05 [Bug target/109971] New: " seurer at gcc dot gnu.org 2023-05-25 22:32 ` [Bug target/109971] " juzhe.zhong at rivai dot ai 2023-05-25 22:32 ` juzhe.zhong at rivai dot ai 2023-05-26 1:15 ` linkw at gcc dot gnu.org 2023-05-26 1:51 ` juzhe.zhong at rivai dot ai 2023-05-26 5:20 ` linkw at gcc dot gnu.org 2023-05-26 5:28 ` juzhe.zhong at rivai dot ai [this message] 2023-05-26 6:22 ` rguenth at gcc dot gnu.org 2023-05-31 2:50 ` linkw at gcc dot gnu.org 2023-05-31 2:54 ` juzhe.zhong at rivai dot ai 2023-05-31 3:11 ` linkw at gcc dot gnu.org 2023-06-02 11:50 ` cvs-commit at gcc dot gnu.org 2023-07-15 6:01 ` pinskia at gcc dot gnu.org 2023-07-17 2:24 ` linkw 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-109971-4-AkYV0J1ncc@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).