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 target/104511] [10/11 Regression] ICE: in emit_move_insn, at expr.cc:4010 with __builtin_convertvector() at -O Date: Wed, 16 Mar 2022 08:22:29 +0000 [thread overview] Message-ID: <bug-104511-4-4tNNBjN2Ne@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104511-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104511 --- Comment #3 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:d261855943584e25c43fc59dfbc75e50e24a66b8 commit r11-9660-gd261855943584e25c43fc59dfbc75e50e24a66b8 Author: Richard Biener <rguenther@suse.de> Date: Mon Feb 14 10:09:10 2022 +0100 tree-optimization/104511 - avoid FP to DFP conversion for VEC_PACK_TRUNC This avoids forwprop from matching DFP <-> FP vector conversions using VEC_[UN]PACK{_TRUNC,_LO,_HI}. Maybe DFP vectors shouldn't be a thing, but they appearantly are. Re-using CONVERT/NOP_EXPR for DFP <-> FP conversions was probably a mistake. 2022-02-14 Richard Biener <rguenther@suse.de> PR tree-optimization/104511 * tree-ssa-forwprop.c (simplify_vector_constructor): Avoid touching DFP <-> FP conversions. * gcc.dg/pr104511.c: New testcase. (cherry picked from commit f320197c8b495324dc6997a99d53e7f45ecf5840)
next prev parent reply other threads:[~2022-03-16 8:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-12 8:05 [Bug target/104511] New: [10/11/12 " zsojka at seznam dot cz 2022-02-14 8:53 ` [Bug target/104511] " rguenth at gcc dot gnu.org 2022-02-14 10:26 ` cvs-commit at gcc dot gnu.org 2022-02-14 10:26 ` [Bug target/104511] [10/11 " rguenth at gcc dot gnu.org 2022-03-16 8:22 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-16 9:22 ` [Bug target/104511] [10 " cvs-commit at gcc dot gnu.org 2022-03-16 9:24 ` 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-104511-4-4tNNBjN2Ne@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).