public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/43175] __builtin_ia32_vec_perm_v4si doesn't work with AVX
Date: Thu, 25 Feb 2010 15:30:00 -0000 [thread overview]
Message-ID: <20100225153006.29280.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43175-682@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from hjl dot tools at gmail dot com 2010-02-25 15:30 -------
(In reply to comment #4)
> I think that this code:
>
> i[0].s[0] = 0;
> i[0].s[1] = 1;
> i[0].s[2] = 2;
> i[0].s[3] = 3;
> i[0].s[4] = 4;
> i[0].s[5] = 5;
> i[0].s[6] = 6;
> i[0].s[7] = 7;
>
> is also wrong. You have i[1].s[4].
>
This testcase is extracted out of gcc.target/i386/vperm-v4si-2.c.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43175
next prev parent reply other threads:[~2010-02-25 15:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 14:48 [Bug target/43175] New: " hjl dot tools at gmail dot com
2010-02-25 14:53 ` [Bug target/43175] " hjl dot tools at gmail dot com
2010-02-25 14:55 ` hjl dot tools at gmail dot com
2010-02-25 15:07 ` hjl dot tools at gmail dot com
2010-02-25 15:10 ` ubizjak at gmail dot com
2010-02-25 15:30 ` hjl dot tools at gmail dot com [this message]
2010-02-25 19:01 ` ubizjak at gmail dot com
2010-02-25 19:03 ` ubizjak at gmail dot com
2010-02-25 19:25 ` hjl dot tools at gmail dot com
2010-02-25 19:34 ` [Bug target/43175] __builtin_ia32_vec_perm_v4si doesn't work with -msse4.1 hjl dot tools at gmail dot com
2010-02-25 19:44 ` ubizjak at gmail dot com
2010-02-25 19:55 ` hjl dot tools at gmail dot com
2010-02-25 20:12 ` ubizjak at gmail dot com
2010-02-25 20:33 ` hjl dot tools at gmail dot com
2010-02-25 20:36 ` hjl dot tools at gmail dot com
2010-02-25 20:49 ` ubizjak at gmail dot com
2010-02-26 0:54 ` hjl dot tools at gmail dot com
2010-02-26 13:19 ` hjl at gcc dot gnu dot org
2010-03-02 13:31 ` hjl dot tools 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=20100225153006.29280.qmail@sourceware.org \
--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: link
Be 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).