3dnow, 3dnow+

[skeltic]

How much harder would it be to translate sse3 to 3dnow+?

[urielka]

3dnow is MMX compatible, MMX is slow,3dnow is ok,3dnow+ is ok+ but sse1/2 are faster,maybe you can make a dual impletion of SSE3 ->SSE2,SSE3->3DNOW+ for more speed on AMD SSE2 CPUS.

Note:you can`t get a full SSE2/3 -> 3dnow/3dnow+ at resonable speed.

SSE2 is very large not like SSE3 that are only 10 commands(+3 Intel Spesific)

[zorxd]

Man you don't know how much work it would be. Making a SSE2 to SSE1 patch would be impossible (or slow as hell), so immagine how hard it would be to make a SSE2 to 3Dnow+

Anyways not everybody has an AMD CPU so it would not worth it.

 

I guess you are better to write an OS X clone from scratch

[plonkersaurus]

Its not a SSE 3 patch to SSE2. SSE 2 is just the requirement for OSX to run on x86.

 

As far as i know maxxus would have just translated the SSE3 instructions to x86 instructions, making it slightly slower, or some other extended instructions and some X86 instructions.

 

Each generation of added instructions (MMX, SSE, SSE2, SSE3) adds more instructions to do things faster (normally compound of basic 386 instructions), but it doesnt normally replace older extended instructions.

 

There is no point in doing 3dnow+ as the current version works fine on all x86 processors that osx will run on, and if using 3dnow was possible it would only work on amd processors.

[mikesown]

Pretty hard. They are completly different instruction sets, so your best bet would be to remove all SSE SSE2 and SSE3 instructions and run generic x86 code if anything.