public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50813] gcc.dg/torture/vshuf-{v4di,v8si}.c fail on AVX target Date: Thu, 20 Oct 2011 19:46:00 -0000 [thread overview] Message-ID: <bug-50813-4-EL6qKwNLra@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50813-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50813 Uros Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011-10-20 Ever Confirmed|0 |1 --- Comment #1 from Uros Bizjak <ubizjak at gmail dot com> 2011-10-20 19:45:44 UTC --- The failure manifests as: In file included from vshuf-v4di.c:14:0: vshuf-main.inc: In function ‘test_16’: vshuf-main.inc:28:1: error: unrecognizable insn: (insn 36 39 37 3 (set (reg:V4DI 99) (unspec:V4DI [ (reg:V4DI 66 [ a.8 ]) (reg:V4DI 98) (const_int 32 [0x20]) ] UNSPEC_VPERMTI)) vshuf-main.inc:28 -1 (nil)) vshuf-main.inc:28:1: internal compiler error: in extract_insn, at recog.c:2137 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. -O2 -mavx
next prev parent reply other threads:[~2011-10-20 19:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-20 19:43 [Bug target/50813] New: " ubizjak at gmail dot com 2011-10-20 19:46 ` ubizjak at gmail dot com [this message] 2011-10-20 19:53 ` [Bug target/50813] " jakub at gcc dot gnu.org 2011-10-21 19:33 ` jakub at gcc dot gnu.org 2012-01-20 11:29 ` ubizjak at gmail dot com
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-50813-4-EL6qKwNLra@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).