public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: shawnw@speakeasy.org
To: gcc-gnats@gcc.gnu.org
Subject: target/7693: Typo in i386 mmintrin.h header
Date: Fri, 23 Aug 2002 02:46:00 -0000 [thread overview]
Message-ID: <200208230733.g7N7Xrd02112@speakeasy.org> (raw)
>Number: 7693
>Category: target
>Synopsis: Typo in i386 mmintrin.h header
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Aug 23 00:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Shawn Wagner
>Release: 3.2
>Organization:
>Environment:
System: Linux sherlock.localdomain 2.2.21 #1 Sun Aug 18 11:20:19 PDT 2002 i686 unknown
Architecture: athlon
host: athlon-pc-linux-gnu
build: athlon-pc-linux-gnu
target: athlon-pc-linux-gnu
configured with: ../gcc-3.2/configure --prefix=/usr/local --target=athlon-pc-linux-gnu --with-arch=athlon --enable-threads=posix --disable-nls --with-system-zlib --enable-languages=c,c++,f77 --enable-__cxa_atexit --enable-shared
>Description:
The functions in gcc/config/i386/mmintrin.h for shifting 64 bit values don't
match the names in the Intel x86 instruction set documentation, or what the
Intel compiler accepts. In all 4 relevant functions, the pi64 extension in
the gcc mmintrin.h names should be si64. For example, _mm_sll_pi64() should
be _mm_sll_si64().
Problem is in 3.2 and current cvs HEAD.
>How-To-Repeat:
>Fix:
--- gcc/config/i386/mmintrin.h.orig Fri Aug 23 00:06:52 2002
+++ gcc/config/i386/mmintrin.h Fri Aug 23 00:10:40 2002
@@ -293,13 +293,13 @@
/* Shift the 64-bit value in M left by COUNT. */
static __inline __m64
-_mm_sll_pi64 (__m64 __m, __m64 __count)
+_mm_sll_si64 (__m64 __m, __m64 __count)
{
return (__m64) __builtin_ia32_psllq (__m, __count);
}
static __inline __m64
-_mm_slli_pi64 (__m64 __m, int __count)
+_mm_slli_si64 (__m64 __m, int __count)
{
return (__m64) __builtin_ia32_psllq (__m, __count);
}
@@ -358,13 +358,13 @@
/* Shift the 64-bit value in M left by COUNT; shift in zeros. */
static __inline __m64
-_mm_srl_pi64 (__m64 __m, __m64 __count)
+_mm_srl_si64 (__m64 __m, __m64 __count)
{
return (__m64) __builtin_ia32_psrlq (__m, __count);
}
static __inline __m64
-_mm_srli_pi64 (__m64 __m, int __count)
+_mm_srli_si64 (__m64 __m, int __count)
{
return (__m64) __builtin_ia32_psrlq (__m, __count);
}
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-08-23 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 2:46 shawnw [this message]
2002-10-03 10:39 hubicka
2002-10-27 2:24 hubicka
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=200208230733.g7N7Xrd02112@speakeasy.org \
--to=shawnw@speakeasy.org \
--cc=gcc-gnats@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).