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/114672] during GIMPLE pass: widening_mul ICE: verify_gimple failed: type mismatch in 'widen_mult_plus_expr' at -O2 Date: Thu, 02 May 2024 19:21:48 +0000 [thread overview] Message-ID: <bug-114672-4-vhNAOX5dCv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114672-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114672 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Richard Ball <ricbal02@gcc.gnu.org>: https://gcc.gnu.org/g:0d625dc1bffd885b04eb90ff48a6d34acacc3e0b commit r13-8676-g0d625dc1bffd885b04eb90ff48a6d34acacc3e0b Author: Richard Biener <rguenther@suse.de> Date: Wed Apr 10 10:33:40 2024 +0200 tree-optimization/114672 - WIDEN_MULT_PLUS_EXPR type mismatch The following makes sure to restrict WIDEN_MULT*_EXPR to a mode precision final compute type as the mode is used to find the optab and type checking chokes when seeing bit-precisions later which would likely also not properly expanded to RTL. PR tree-optimization/114672 * tree-ssa-math-opts.cc (convert_plusminus_to_widen): Only allow mode-precision results. * gcc.dg/torture/pr114672.c: New testcase. (cherry picked from commit 912753cc5f18d786e334dd425469fa7f93155661)
next prev parent reply other threads:[~2024-05-02 19:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-10 4:17 [Bug tree-optimization/114672] New: " zsojka at seznam dot cz 2024-04-10 8:17 ` [Bug tree-optimization/114672] " rguenth at gcc dot gnu.org 2024-04-10 16:43 ` cvs-commit at gcc dot gnu.org 2024-04-10 16:44 ` rguenth at gcc dot gnu.org 2024-05-02 12:37 ` ricbal02 at gcc dot gnu.org 2024-05-02 19:21 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-02 19:23 ` cvs-commit 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-114672-4-vhNAOX5dCv@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).