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/114471] [14 regression] ICE when building liblc3-1.0.4 with -fno-vect-cost-model -march=x86-64-v4 Date: Tue, 26 Mar 2024 10:06:02 +0000 [thread overview] Message-ID: <bug-114471-4-x61fdgeQ5T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114471-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114471 --- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:f4e92d62dccb96ade753f3a8f49be1b5f61c31f1 commit r14-9666-gf4e92d62dccb96ade753f3a8f49be1b5f61c31f1 Author: Richard Biener <rguenther@suse.de> Date: Tue Mar 26 09:11:00 2024 +0100 tree-optimization/114471 - ICE with mismatching vector types The following fixes too lax verification of vector type compatibility in vectorizable_operation. When we only have a single vector size then comparing the number of elements is enough but with SLP we mix those and thus for operations like BIT_AND_EXPR we need to verify compatible element types as well. Allow sign changes for ABSU_EXPR though. PR tree-optimization/114471 * tree-vect-stmts.cc (vectorizable_operation): Verify operand types are compatible with the result type. * gcc.dg/vect/pr114471.c: New testcase.
next prev parent reply other threads:[~2024-03-26 10:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-25 17:18 [Bug tree-optimization/114471] New: [14 regression] ICE when building liblc3-1.0.4 sjames at gcc dot gnu.org 2024-03-25 17:20 ` [Bug tree-optimization/114471] [14 regression] ICE when building liblc3-1.0.4 with -fno-vect-cost-model -march=x86-64-v4 sjames at gcc dot gnu.org 2024-03-25 17:21 ` sjames at gcc dot gnu.org 2024-03-25 18:02 ` sjames at gcc dot gnu.org 2024-03-25 22:51 ` pinskia at gcc dot gnu.org 2024-03-26 3:58 ` liuhongt at gcc dot gnu.org 2024-03-26 4:09 ` liuhongt at gcc dot gnu.org 2024-03-26 7:58 ` rguenth at gcc dot gnu.org 2024-03-26 10:06 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-26 10:07 ` 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-114471-4-x61fdgeQ5T@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).