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/97236] [10/11 Regression] g:e93428a8b056aed83a7678 triggers vlc miscompile Date: Thu, 01 Oct 2020 13:58:39 +0000 [thread overview] Message-ID: <bug-97236-4-x3QkLKycwb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97236-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97236 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:04b99da898a9817e72fedb4063589648b7961ac5 commit r11-3594-g04b99da898a9817e72fedb4063589648b7961ac5 Author: Richard Biener <rguenther@suse.de> Date: Thu Oct 1 15:12:35 2020 +0200 tree-optimization/97236 - fix bad use of VMAT_CONTIGUOUS This avoids using VMAT_CONTIGUOUS with single-element interleaving when using V1mode vectors. Instead keep VMAT_ELEMENTWISE but continue to avoid load-lanes and gathers. 2020-10-01 Richard Biener <rguenther@suse.de> PR tree-optimization/97236 * tree-vect-stmts.c (get_group_load_store_type): Keep VMAT_ELEMENTWISE for single-element vectors. * gcc.dg/vect/pr97236.c: New testcase.
next prev parent reply other threads:[~2020-10-01 13:58 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-29 7:12 [Bug tree-optimization/97236] New: " rguenth at gcc dot gnu.org 2020-09-29 7:13 ` [Bug tree-optimization/97236] " rguenth at gcc dot gnu.org 2020-09-29 13:05 ` marxin at gcc dot gnu.org 2020-09-29 13:05 ` marxin at gcc dot gnu.org 2020-09-29 13:06 ` marxin at gcc dot gnu.org 2020-09-29 13:46 ` rguenth at gcc dot gnu.org 2020-09-29 14:14 ` rguenth at gcc dot gnu.org 2020-09-30 9:20 ` rguenth at gcc dot gnu.org 2020-10-01 13:58 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-01 13:59 ` [Bug tree-optimization/97236] [10 " rguenth at gcc dot gnu.org 2020-10-06 11:42 ` cvs-commit at gcc dot gnu.org 2020-10-06 12:20 ` rguenth at gcc dot gnu.org 2021-02-03 8:25 ` rguenth at gcc dot gnu.org 2021-02-03 8:26 ` [Bug tree-optimization/97236] [8/9 " rguenth at gcc dot gnu.org 2021-02-05 15:43 ` cvs-commit at gcc dot gnu.org 2021-02-05 15:44 ` ktkachov at gcc dot gnu.org 2021-02-05 15:45 ` [Bug tree-optimization/97236] [8 " ktkachov at gcc dot gnu.org 2021-02-08 10:33 ` cvs-commit at gcc dot gnu.org 2021-02-08 10:43 ` rguenth at gcc dot gnu.org 2021-03-04 8:06 ` marxin at gcc dot gnu.org 2021-04-19 6:31 ` 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-97236-4-x3QkLKycwb@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).