public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/46419] [4.4, 4.5, 4.6 Regression] _mm_cvtpu16_ps (and hence _mm_cvtpu8_ps) returns false result Date: Wed, 10 Nov 2010 23:28:00 -0000 [thread overview] Message-ID: <bug-46419-4-Gy5bURcIQo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46419-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46419 --- Comment #4 from uros at gcc dot gnu.org 2010-11-10 23:28:10 UTC --- Author: uros Date: Wed Nov 10 23:28:03 2010 New Revision: 166572 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166572 Log: PR middle-end/46419 * config/i386/xmmintrin.h (_mm_cvtpi16_ps): Swap __hisi and __losi. (_mm_cvtpu16_ps): Ditto. testsuite/ChangeLog: PR target/46419 * gcc-target/i386/pr46419.c: New test. Added: branches/gcc-4_4-branch/gcc/testsuite/gcc.target/i386/pr46419.c - copied unchanged from r166569, trunk/gcc/testsuite/gcc.target/i386/pr46419.c Modified: branches/gcc-4_4-branch/gcc/ChangeLog branches/gcc-4_4-branch/gcc/config/i386/xmmintrin.h branches/gcc-4_4-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2010-11-10 23:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-10 20:39 [Bug c/46419] New: xmmintrin.h: _mm_cvtpu16_ps (and hence _mm_cvtpu8_ps) returns false result in gcc >= 4.4 release_candidate at yahoo dot com 2010-11-10 22:14 ` [Bug target/46419] [4.4, 4.5, 4.6 Regression] _mm_cvtpu16_ps (and hence _mm_cvtpu8_ps) returns false result ubizjak at gmail dot com 2010-11-10 23:00 ` uros at gcc dot gnu.org 2010-11-10 23:27 ` uros at gcc dot gnu.org 2010-11-10 23:28 ` uros at gcc dot gnu.org [this message] 2010-11-10 23:30 ` ubizjak at gmail dot com 2011-03-09 16:42 ` 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-46419-4-Gy5bURcIQo@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).