Re: Why ssse3?
> 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. ... and just to make things more fun, SSE4 is sometimes called Penryn New Instructions -- PNI all over again. - R. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why ssse3?
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why ssse3?
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. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why ssse3?
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. -Andi - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why ssse3?
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 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why ssse3?
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. ... and just to make things more fun, SSE4 is sometimes called Penryn New Instructions -- PNI all over again. - R. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why ssse3?
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. Intel has a nasty habit of renaming things after they are already deployed in Linux. -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why ssse3?
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. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ signature.asc Description: OpenPGP digital signature
Re: Why ssse3?
On Thursday 03 May 2007 00:41:22 Ulrich Drepper wrote: > Note the extra 's'. We use "sse" and "sse2", but "ssse3". I assume > it's a typo. Nope. SSE3 != SSSE3. The additional S means Supplemential. It's probably because the few changes didn't justify a SSE4 -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why ssse3?
On Thursday 03 May 2007 01:41:22 Ulrich Drepper wrote: > Note the extra 's'. We use "sse" and "sse2", but "ssse3". I assume > it's a typo. This might not be a typo see http://en.wikipedia.org/wiki/SSSE3 Regards, ismail signature.asc Description: This is a digitally signed message part.
Re: Why ssse3?
On Thursday 03 May 2007 01:41:22 Ulrich Drepper wrote: Note the extra 's'. We use sse and sse2, but ssse3. I assume it's a typo. This might not be a typo see http://en.wikipedia.org/wiki/SSSE3 Regards, ismail signature.asc Description: This is a digitally signed message part.
Re: Why ssse3?
On Thursday 03 May 2007 00:41:22 Ulrich Drepper wrote: Note the extra 's'. We use sse and sse2, but ssse3. I assume it's a typo. Nope. SSE3 != SSSE3. The additional S means Supplemential. It's probably because the few changes didn't justify a SSE4 -Andi - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why ssse3?
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. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ signature.asc Description: OpenPGP digital signature
Re: Why ssse3?
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. Intel has a nasty habit of renaming things after they are already deployed in Linux. -hpa - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
