public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aivchenk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/53435] New: (ix86_expand_vec_perm) and (ix86_expand_vec_perm) do not pass arguments to avx2_permvar8s[f,i] correctly Date: Mon, 21 May 2012 12:37:00 -0000 [thread overview] Message-ID: <bug-53435-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53435 Bug #: 53435 Summary: (ix86_expand_vec_perm) and (ix86_expand_vec_perm) do not pass arguments to avx2_permvar8s[f,i] correctly Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: aivchenk@gmail.com CC: areg.melikadamyan@gmail.com, hjl.tools@gmail.com, kirill.yukhin@intel.com, ubizjak@gmail.com Target: i?86-*-* x86_64-*-* Seems that after: commit 8da8a06b586ddd9511b5c5c83e2c28ca8d7613a8 Author: uros <uros@138bc75d-0d04-0410-961f-82ee72b054a4> Date: Thu Apr 12 18:37:42 2012 +0000 PR target/52932 * config/i386/avx2intrin.h (_mm256_permutevar8x32_ps): Change second argument type to __m256i. Update call to __builtin_ia32_permvarsf256. ... (avx2_permvarv8sf, avx2_permvarv8si): Switch operands 1 and 2. ... (ix86_expand_vec_perm): Update calls to gen_avx2_permvarv8si and gen_avx2_permvarv8sf. (expand_vec_perm_pshufb): Ditto. gcc.c-torture/execute/vshuf-v* and gcc.dg/torture/pr45720.c fail. The problem is that not everything that had to be changed was changed to use the second argument as __m256i. Please take a look at the attached patch that should fix those problems
next reply other threads:[~2012-05-21 12:37 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-21 12:37 aivchenk at gmail dot com [this message] 2012-05-21 12:39 ` [Bug target/53435] " kirill.yukhin at intel dot com 2012-05-21 12:44 ` aivchenk at gmail dot com 2012-05-21 13:21 ` hjl.tools at gmail dot com 2012-05-25 13:15 ` kyukhin at gcc dot gnu.org 2012-05-25 13:39 ` kyukhin at gcc dot gnu.org 2012-12-04 19:18 ` glisse at gcc dot gnu.org 2012-12-04 19:31 ` 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-53435-4@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).