public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/48616] -ftree-vectorize -mxop miscompiles right shift Date: Mon, 18 Apr 2011 06:56:00 -0000 [thread overview] Message-ID: <bug-48616-4-t9HQD4BvgG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48616-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48616 --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-04-18 06:55:17 UTC --- Author: jakub Date: Mon Apr 18 06:55:13 2011 New Revision: 172638 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=172638 Log: PR tree-optimization/48616 * tree-vect-stmts.c (vectorizable_shift): If SLP, determine whether the shift is by scalar or vector based on whether all SLP scalar stmts have the same rhs. * gcc.dg/pr48616.c: New test. Added: trunk/gcc/testsuite/gcc.dg/pr48616.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-vect-stmts.c
next prev parent reply other threads:[~2011-04-18 6:56 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-15 8:16 [Bug tree-optimization/48616] New: " kretz at kde dot org 2011-04-15 10:38 ` [Bug tree-optimization/48616] " rguenth at gcc dot gnu.org 2011-04-15 11:37 ` jakub at gcc dot gnu.org 2011-04-15 12:11 ` kretz at kde dot org 2011-04-15 12:32 ` jakub at gcc dot gnu.org 2011-04-15 13:08 ` jakub at gcc dot gnu.org 2011-04-15 13:39 ` jakub at gcc dot gnu.org 2011-04-15 16:03 ` jakub at gcc dot gnu.org 2011-04-15 16:56 ` jakub at gcc dot gnu.org 2011-04-15 19:09 ` jakub at gcc dot gnu.org 2011-04-15 20:10 ` rguenth at gcc dot gnu.org 2011-04-18 6:56 ` jakub at gcc dot gnu.org [this message] 2011-04-18 7:43 ` jakub at gcc dot gnu.org 2011-04-18 7:44 ` jakub at gcc dot gnu.org 2011-04-18 17:01 ` kretz at kde dot 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-48616-4-t9HQD4BvgG@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).