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/99856] [9 Regression] Alpha Compositing auto vectorization regression Date: Thu, 01 Apr 2021 09:42:53 +0000 [thread overview] Message-ID: <bug-99856-4-xmGMyiXPFc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99856-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99856 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:3d705c86c08985af73823b71af21c2ffe2c23758 commit r9-9317-g3d705c86c08985af73823b71af21c2ffe2c23758 Author: Richard Biener <rguenther@suse.de> Date: Thu Apr 1 09:29:14 2021 +0200 tree-optimization/99856 - fix overwideing pattern creation This fixes an omission of promoting a bit-precision required precision to a vector element precision. 2021-04-01 Richard Biener <rguenther@suse.de> PR tree-optimization/99856 * tree-vect-patterns.c (vect_recog_over_widening_pattern): Promote precision to vector element precision. * gcc.dg/vect/pr99856.c: New testcase. (cherry picked from commit 1cfe48d35e31e905632e37ae6a9cb37d35f9a228)
next prev parent reply other threads:[~2021-04-01 9:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 20:24 [Bug c/99856] New: Alpha Compositing auto vectorization regression: 8.3 -> 9.1 dushistov at mail dot ru 2021-04-01 4:42 ` [Bug tree-optimization/99856] [9/10/11 Regression] Alpha Compositing auto vectorization regression marxin at gcc dot gnu.org 2021-04-01 7:21 ` rguenth at gcc dot gnu.org 2021-04-01 8:23 ` cvs-commit at gcc dot gnu.org 2021-04-01 9:14 ` [Bug tree-optimization/99856] [9/10 " cvs-commit at gcc dot gnu.org 2021-04-01 9:42 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-01 9:43 ` [Bug tree-optimization/99856] [9 " 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-99856-4-xmGMyiXPFc@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).