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/109473] [10/11 Regression] ICE during GIMPLE pass: vect: verify_gimple failed with -O1 -ftree-loop-vectorize since r10-4076-g82e8e335f917b9 Date: Tue, 02 May 2023 12:03:54 +0000 [thread overview] Message-ID: <bug-109473-4-xUv8tAOfg7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109473-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109473 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:54ddf6426e04e4b0d24bbc7e37d40acbf5fbfe3b commit r11-10676-g54ddf6426e04e4b0d24bbc7e37d40acbf5fbfe3b Author: Richard Biener <rguenther@suse.de> Date: Wed Apr 12 10:22:08 2023 +0200 tree-optimization/109473 - ICE with reduction epilog adjustment op The following makes sure to carry out the reduction epilog adjustment in the original computation type which for pointers is an unsigned integer type. There's a similar issue with signed vs. unsigned ops and overflow which is fixed by this as well. PR tree-optimization/109473 * tree-vect-loop.c (vect_create_epilog_for_reduction): Convert scalar result to the computation type before performing the reduction adjustment. * gcc.dg/vect/pr109473.c: New testcase. (cherry picked from commit df7f55cb2ae550adeda339a57b657ebe1ad39367)
next prev parent reply other threads:[~2023-05-02 12:03 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-11 14:48 [Bug tree-optimization/109473] New: ICE during GIMPLE pass: vect: verify_gimple failed with -m32 arsen at gcc dot gnu.org 2023-04-11 14:55 ` [Bug tree-optimization/109473] ICE during GIMPLE pass: vect: verify_gimple failed with -O1 -ftree-loop-vectorize arsen at gcc dot gnu.org 2023-04-11 15:13 ` [Bug tree-optimization/109473] [10/11/12/13 Regression] " jakub at gcc dot gnu.org 2023-04-12 8:00 ` [Bug tree-optimization/109473] [10/11/12/13 Regression] ICE during GIMPLE pass: vect: verify_gimple failed with -O1 -ftree-loop-vectorize since r10-4076-g82e8e335f917b9 rguenth at gcc dot gnu.org 2023-04-12 8:06 ` jakub at gcc dot gnu.org 2023-04-12 10:23 ` cvs-commit at gcc dot gnu.org 2023-04-12 10:24 ` [Bug tree-optimization/109473] [10/11/12 " rguenth at gcc dot gnu.org 2023-04-12 10:53 ` arsen at gcc dot gnu.org 2023-04-17 9:14 ` cvs-commit at gcc dot gnu.org 2023-05-02 12:03 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-03 8:45 ` [Bug tree-optimization/109473] [10 " jakub at gcc dot gnu.org 2023-05-03 10:14 ` cvs-commit at gcc dot gnu.org 2023-07-07 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-109473-4-xUv8tAOfg7@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).