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 tree-optimization/108608] [12 Regression] AArch64 vectorizer ICE in vect_transform_reduction and __builtin_fmax Date: Mon, 03 Apr 2023 08:58:00 +0000 [thread overview] Message-ID: <bug-108608-4-TnYJ0XmhxU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108608-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108608 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:65216cd44b8c89640ad987b6227ea1d748456a41 commit r12-9381-g65216cd44b8c89640ad987b6227ea1d748456a41 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Mon Apr 3 09:57:07 2023 +0100 vect: Fix single def-use cycle for ifn reductions [PR108608] The patch that added support for fmin/fmax reductions didn't handle single def-use cycles. In some ways, this seems like going out of our way to make things slower, but that's a discussion for another day. gcc/ PR tree-optimization/108608 * tree-vect-loop.cc (vect_transform_reduction): Handle single def-use cycles that involve function calls rather than tree codes. gcc/testsuite/ PR tree-optimization/108608 * gcc.dg/vect/pr108608.c: New test. * gcc.target/aarch64/sve/pr108608-1.c: Likewise. (cherry picked from commit 2bb444787ed17a9e786f544cdf51ee2ac6779ab2)
next prev parent reply other threads:[~2023-04-03 8:58 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-30 21:49 [Bug tree-optimization/108608] New: [12/13 Regression] AArch64 vectorizer ICE in vect_transform_reduction jakub at gcc dot gnu.org 2023-01-30 21:50 ` [Bug tree-optimization/108608] " jakub at gcc dot gnu.org 2023-01-30 21:55 ` [Bug tree-optimization/108608] [12/13 Regression] AArch64 vectorizer ICE in vect_transform_reduction and __builtin_fmax jakub at gcc dot gnu.org 2023-01-30 21:59 ` pinskia at gcc dot gnu.org 2023-01-30 22:03 ` pinskia at gcc dot gnu.org 2023-01-30 22:09 ` jakub at gcc dot gnu.org 2023-01-30 22:14 ` jakub at gcc dot gnu.org 2023-01-30 22:51 ` rsandifo at gcc dot gnu.org 2023-01-31 15:03 ` cvs-commit at gcc dot gnu.org 2023-04-03 8:58 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-03 9:03 ` [Bug tree-optimization/108608] [12 " rsandifo 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-108608-4-TnYJ0XmhxU@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).