From: Andi Kleen <ak@suse.de>
To: Avi Kivity <avi@argo.co.il>
Cc: Ulrich Drepper <drepper@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Why ssse3?
Date: Thu, 3 May 2007 11:07:39 +0200 [thread overview]
Message-ID: <200705031107.39609.ak@suse.de> (raw)
In-Reply-To: <4639A527.5080909@argo.co.il>
On Thursday 03 May 2007 11:02:31 Avi Kivity wrote:
> Andi Kleen wrote:
> > On Thursday 03 May 2007 00:56:26 Ulrich Drepper wrote:
> >
> >> Andi Kleen wrote:
> >>
> >>> Nope. SSE3 != SSSE3. The additional S means Supplemential.
> >>>
> >>> It's probably because the few changes didn't justify a SSE4
> >>>
> >> OK, the problem is that the actual sse3 bit is misnamed. According to
> >> Intel's docs bit 0 of ECX is "sse", the kernel uses "pni". Too bad.
> >>
> >
> > PNI (Prescott New Instructions) was the original engineering code name. Unfortunately
> > it was added too early before the marketing name was known and then it couldn't be
> > changed anymore.
> >
>
> Perhaps sse3 could be added as an alias to pni.
That was considered at some point, but it would be a ugly special case and is
probably not worth it. Usually these flags are Greek for most people anyways
(and something else for the Greek speaking people @)
-Andi
next prev parent reply other threads:[~2007-05-03 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 22:41 Why ssse3? Ulrich Drepper
2007-05-02 22:46 ` Andi Kleen
2007-05-02 22:56 ` Ulrich Drepper
2007-05-03 2:28 ` H. Peter Anvin
2007-05-03 8:52 ` Andi Kleen
2007-05-03 9:02 ` Avi Kivity
2007-05-03 9:07 ` Andi Kleen [this message]
2007-05-03 16:03 ` Roland Dreier
2007-05-02 22:47 ` Ismail Dönmez
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=200705031107.39609.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=avi@argo.co.il \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.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