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/111414] [14 Regression] ICE in verify_gimple failed since r14-3719-gb34f3736356 Date: Fri, 15 Sep 2023 14:27:28 +0000 [thread overview] Message-ID: <bug-111414-4-j1JcnM1udK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111414-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111414 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:ba4c1f2bfc9ec063188b39d0281fae04c57b1416 commit r14-4037-gba4c1f2bfc9ec063188b39d0281fae04c57b1416 Author: Andrew Pinski <apinski@marvell.com> Date: Thu Sep 14 07:39:31 2023 -0700 MATCH: Fix `(1 >> X) != 0` pattern for vector types I had missed that integer_onep can match vector types with uniform constant of `1`. This means the shifter could be an scalar type and then doing a comparison against `0` would be an invalid transformation. This fixes the problem by adding a check for the type of the integer_onep to make sure it is a INTEGRAL_TYPE_P (which does not match a vector type). OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions. PR tree-optimization/111414 gcc/ChangeLog: * match.pd (`(1 >> X) != 0`): Check to see if the integer_onep was an integral type (not a vector type). gcc/testsuite/ChangeLog: * gcc.c-torture/compile/pr111414-1.c: New test.
next prev parent reply other threads:[~2023-09-15 14:27 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-14 10:57 [Bug tree-optimization/111414] New: " shaohua.li at inf dot ethz.ch 2023-09-14 12:06 ` [Bug tree-optimization/111414] [14 Regression] " rguenth at gcc dot gnu.org 2023-09-14 14:07 ` pinskia at gcc dot gnu.org 2023-09-14 14:38 ` pinskia at gcc dot gnu.org 2023-09-14 17:49 ` pinskia at gcc dot gnu.org 2023-09-15 14:27 ` cvs-commit at gcc dot gnu.org [this message] 2023-09-15 14:28 ` pinskia 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-111414-4-j1JcnM1udK@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).