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 target/50911] [4.7 regression] assertion failure in expand_vec_perm_interleave2 with -msse Date: Wed, 09 Nov 2011 21:51:00 -0000 [thread overview] Message-ID: <bug-50911-4-b73zR4CXoK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50911-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50911 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-11-09 21:37:31 UTC --- Author: jakub Date: Wed Nov 9 21:37:27 2011 New Revision: 181238 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=181238 Log: PR target/50911 * config/i386/i386.c (expand_vec_perm_interleave2): If d->vmode is V4SImode, !TARGET_SSE2 and punpck[lh]* is needed, change dremap.vmode to V4SFmode. * gcc.dg/torture/vshuf-16.inc: Add interleave low and high permutations. * gcc.dg/torture/vshuf-32.inc: Likewise. * gcc.dg/torture/vshuf-4.inc: Likewise. * gcc.dg/torture/vshuf-8.inc: Likewise. Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/torture/vshuf-16.inc trunk/gcc/testsuite/gcc.dg/torture/vshuf-32.inc trunk/gcc/testsuite/gcc.dg/torture/vshuf-4.inc trunk/gcc/testsuite/gcc.dg/torture/vshuf-8.inc
next prev parent reply other threads:[~2011-11-09 21:38 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-29 15:14 [Bug target/50911] New: " ebotcazou at gcc dot gnu.org 2011-10-30 9:16 ` [Bug target/50911] " rguenth at gcc dot gnu.org 2011-11-05 11:59 ` rguenth at gcc dot gnu.org 2011-11-09 13:57 ` jakub at gcc dot gnu.org 2011-11-09 15:11 ` jakub at gcc dot gnu.org 2011-11-09 18:31 ` jakub at gcc dot gnu.org 2011-11-09 21:51 ` jakub at gcc dot gnu.org [this message] 2011-11-09 21:54 ` jakub 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-50911-4-b73zR4CXoK@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).