linux-kernel - Re: Why ssse3?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4639A527.5080909@argo.co.il>
Date:	Thu, 03 May 2007 12:02:31 +0300
From:	Avi Kivity <avi@...o.co.il>
To:	Andi Kleen <ak@...e.de>
CC:	Ulrich Drepper <drepper@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Why ssse3?

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.


-- 
error compiling committee.c: too many arguments to function

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/