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/114883] [14/15 Regression] 521.wrf_r ICE with -O2 -march=sapphirerapids -fvect-cost-model=cheap Date: Tue, 30 Apr 2024 08:16:13 +0000 [thread overview] Message-ID: <bug-114883-4-i072NqO3Uv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114883-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114883 --- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-14 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:a795a7b67027bc976a353b5fa927ac8c5f29347d commit r14-10152-ga795a7b67027bc976a353b5fa927ac8c5f29347d Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 30 10:11:47 2024 +0200 vect: Adjust vect_transform_reduction assertion [PR114883] The assertion doesn't allow IFN_COND_MIN/IFN_COND_MAX, which are commutative conditional binary operations like ADD/MUL/AND/IOR/XOR, and can be handled just fine. In particular, we emit vminpd %zmm3, %zmm5, %zmm0{%k2} vminpd %zmm0, %zmm3, %zmm5{%k1} and vmaxpd %zmm3, %zmm5, %zmm0{%k2} vmaxpd %zmm0, %zmm3, %zmm5{%k1} in the vectorized loops of the first and second subroutine. 2024-04-30 Jakub Jelinek <jakub@redhat.com> Hongtao Liu <hongtao.liu@intel.com> PR tree-optimization/114883 * tree-vect-loop.cc (vect_transform_reduction): Allow IFN_COND_MIN and IFN_COND_MAX in the assert. * gfortran.dg/pr114883.f90: New test. (cherry picked from commit 04ef92a62af3a815b86a2037267cd4e747ae225c)
next prev parent reply other threads:[~2024-04-30 8:16 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-29 4:42 [Bug tree-optimization/114883] New: " liuhongt at gcc dot gnu.org 2024-04-29 4:44 ` [Bug tree-optimization/114883] [14 Regression] " pinskia at gcc dot gnu.org 2024-04-29 4:45 ` [Bug tree-optimization/114883] [14/15 " pinskia at gcc dot gnu.org 2024-04-29 4:52 ` liuhongt at gcc dot gnu.org 2024-04-29 5:44 ` liuhongt at gcc dot gnu.org 2024-04-29 8:44 ` liuhongt at gcc dot gnu.org 2024-04-29 8:52 ` liuhongt at gcc dot gnu.org 2024-04-29 17:18 ` jakub at gcc dot gnu.org 2024-04-29 17:41 ` jakub at gcc dot gnu.org 2024-04-29 17:50 ` jakub at gcc dot gnu.org 2024-04-29 18:44 ` jakub at gcc dot gnu.org 2024-04-30 0:43 ` liuhongt at gcc dot gnu.org 2024-04-30 8:12 ` cvs-commit at gcc dot gnu.org 2024-04-30 8:16 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-30 8:16 ` jakub 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-114883-4-i072NqO3Uv@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).