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 c/113134] gcc does not version loops with early break conditions that don't have side-effects Date: Thu, 28 Dec 2023 01:21:38 +0000 [thread overview] Message-ID: <bug-113134-4-5L1TxjI6B4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113134-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113134 --- Comment #3 from JuzheZhong <juzhe.zhong at rivai dot ai> --- Thanks Tamar. And I agree with you. This is not supposed to let early break to handle that. It should be optimization on scalar IR instead of loop vectorizer. I believe it is GCC-15 topic. Btw, I am trying to enable early break on RISC-V port. But I failed to do that since this following codes look quite to length target: if (LOOP_VINFO_CAN_USE_PARTIAL_VECTORS_P (loop_vinfo)) { if (direct_internal_fn_supported_p (IFN_VCOND_MASK_LEN, vectype, OPTIMIZE_FOR_SPEED)) return false; else vect_record_loop_mask (loop_vinfo, masks, ncopies, vectype, NULL); } I guess this code is just disabling partial vector for length for now. And need me to test and port this part for length in the followup patches. Am I right ?
next prev parent reply other threads:[~2023-12-28 1:21 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-25 11:29 [Bug c/113134] New: Middle end early break vectorization: Fail to vectorize a simple early break code juzhe.zhong at rivai dot ai 2023-12-25 12:35 ` [Bug c/113134] " tnfchris at gcc dot gnu.org 2023-12-27 15:21 ` [Bug c/113134] gcc does not version loops with side-effect early breaks tnfchris at gcc dot gnu.org 2023-12-28 1:21 ` juzhe.zhong at rivai dot ai [this message] 2023-12-28 3:48 ` [Bug c/113134] gcc does not version loops with early break conditions that don't have side-effects tnfchris at gcc dot gnu.org 2023-12-28 3:55 ` juzhe.zhong at rivai dot ai 2023-12-28 4:02 ` tnfchris at gcc dot gnu.org 2023-12-28 4:05 ` tnfchris at gcc dot gnu.org 2023-12-28 4:23 ` juzhe.zhong at rivai dot ai 2023-12-28 4:30 ` tnfchris at gcc dot gnu.org 2023-12-28 4:35 ` juzhe.zhong at rivai dot ai 2023-12-28 4:45 ` tnfchris at gcc dot gnu.org 2023-12-28 4:46 ` juzhe.zhong at rivai dot ai 2023-12-28 4:49 ` tnfchris at gcc dot gnu.org 2023-12-28 4:51 ` juzhe.zhong at rivai dot ai 2023-12-28 4:53 ` tnfchris at gcc dot gnu.org 2023-12-28 5:08 ` tnfchris at gcc dot gnu.org 2023-12-28 9:11 ` juzhe.zhong at rivai dot ai 2023-12-28 21:20 ` [Bug tree-optimization/113134] " pinskia at gcc dot gnu.org 2024-01-08 8:11 ` rguenth at gcc dot gnu.org 2024-01-31 11:48 ` juzhe.zhong at rivai dot ai 2024-01-31 12:04 ` rguenth at gcc dot gnu.org 2024-02-02 3:38 ` juzhe.zhong at rivai dot ai 2024-02-02 8:49 ` 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-113134-4-5L1TxjI6B4@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).