Contents

Talk:SSE3

This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing: Software Low‑importance This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles Low This article has been rated as Low-importance on the project's importance scale. This article is supported by WikiProject Software (assessed as Low-importance). This article is supported by Computer hardware task force (assessed as Low-importance).

added the turion64 :) --??

Suggest adding list of known OSs supporting this feature. --194.249.198.31 12:27, 3 October 2005 (UTC)[reply]

I disagree. SSE3 does not require OS support afaik. --Yamla 13:20, 3 October 2005 (UTC)[reply]

Some instructions, such as MONITOR and MWAIT, are only useful in the operating system proper and libraries where they are used transparently instead of e.g. spinlocks and mutexes. Of course this would require further discussion on how CMP chips (Athlon X2, p4 with hyperthreading, etc) handle inter-thread synchronization and what the two instructions bring to the table with regard to this. Bottom line: I agree, there's no point in mentioning separate operating system _support_, since that is too minor an implementation detail to be notable. A short paragraph on what these instructions do apart from a general statement that they "optimize" this and that would be super nice though. So would a little bit on how the add/sub packed -type instructions may be used to speed up some operations on complex numbers, but then I'd quite like it to rain gold too. (As a historical note, the original SSE did require operating system support to store and reload the registers after a context switch.) --85.76.93.185 20:37, 16 April 2006 (UTC)[reply]

I added the expand tag here because I hope someone can come along and fill in the rest of what the SSE instructions mean in plain English. This has already been partially completed but completely finishing the task would make the article nicer. Triddle 16:49, 28 October 2005 (UTC)[reply]

There should be at least a listing of SSE instructions, and a fairly simple programming example for some of them. mtodorov3_69@yahoo.com

I just noticed that there already is a separate page for the MOVDDUP instruction for example, but it isn't linked to from this article, maybe this could be done and examples could be included in the instruction's page? (AdionC) —Preceding unsigned comment added by AdionC (talk • contribs) 22:00, 16 July 2008 (UTC)[reply]

By the way, tags like the expansion tag should be put in the article, not the talk page. C xong (talk) 04:54, 15 March 2010 (UTC)[reply]

I haven't what it takes to state this succinctly in the article proper, but e.g. MONITOR, MWAIT and FISTTP have next to nothing to do with SIMD, the first two being thread control instructions and the last one an x87 floating-point extension. Though these all fit the label of prescott new instructions, obviously. --85.76.93.185 20:45, 16 April 2006 (UTC)[reply]

The reason why they are in this article, is because Intel says that they are a part of SSE3. Personally, you're more than welcome to write Intel and tell them how useless most of SSE3 is. --Puellanivis 00:26, 6 October 2006 (UTC)[reply]

Does anybody have info on what compilers support generating SSE code? —The preceding unsigned comment was added by 201.213.37.39 (talk) 00:03, August 22, 2007 (UTC)

It would be nice to have a list of programs that take advantage of SSE3. —Preceding unsigned comment added by 86.42.177.201 (talk) 14:28, August 26, 2007 (UTC)
I agree

The OS Moblin require SSE3 to work. www.moblin.org —Preceding unsigned comment added by 83.255.33.14 (talk) 14:13, 1 October 2009 (UTC)[reply]