AMD Processors

[Joe[x86]]

I heard they don't support the full IA32 instruction set. Is this true? What instructions does it not support? I'm looking into getting a new processor in the near future, because I don't feel like ordering a whole new box, but some components are old-ish.

[MyndFyre]

ADD, SUB, etc. 

Usually AMD gets on board with Intel's spec shortly after Intel releases it (note that AMD supports SSE2 and SSE3).  Having said so, I'm relatively sure that they have the same instruction set (at least on x86), and if they have machine code differences they're minimal.  Unfortunately, I'm not down for Google hunting for an answer - three different searches don't turn up much of a result. 

[Stealth]

I don't think AMD's processors would have the market share they do currently if they were handicapped in some way compared to the industry standard.

[warz]

I heard they don't support the full IA32 instruction set. Is this true? What instructions does it not support? I'm looking into getting a new processor in the near future, because I don't feel like ordering a whole new box, but some components are old-ish.

What kind of fraternity is  Sigma upsilon kappa?

[Joe[x86]]

I heard they don't support the full IA32 instruction set. Is this true? What instructions does it not support? I'm looking into getting a new processor in the near future, because I don't feel like ordering a whole new box, but some components are old-ish.

What kind of fraternity is Sigma upsilon kappa?

Sigma upsilon kappa is transliterated to SUK, because Greek lacks a C. I suk.

[Warrior]

Oh god..if there is any difference it would be so minimal you would hardly notice unless you program at the OS level.

[Joe[x86]]

Oh god..if there is any difference it would be so minimal you would hardly notice unless you program at the OS level.

Which is exactly why I asked?

[Warrior]

But you don't program at the low level, either way the differences can be seen by either googling a reference or comparing the AMD Docs to the Intel ones. AMD *should* list somewhere what they break/don't break.

Hint: Until you get really nasty into kernel development this shouldn't matter, with proper architecture branching in your code you should be able to detect processor features by using cpuid and enabling/disabling them at your liking in your system.

[Joe[x86]]

You seem to have forgotten a good 10 hours of your life from a few months ago. I did do pre-kernel development, and you should know that having taught me nearly all that I know.

[Warrior]

I taught you nearly nothing, it much more complicated. It's only the tip of the iceburg, read what I said for your answer.

[Joe[x86]]

Everybody starts somewhere, but yeah. You were a horrible teacher. <3

Thanks guys.