Talk:XOP instruction set

market failure

An anonymous user has removed the section about market failure with the comment ("Market failure" means it's bad for all involved, including intel. That's not obviously the case.), incidentally also removing a reference. I have undone this deletion because it is based on a misunderstanding of what market failure means. Market failure does not mean that it is bad for all involved. See the definition of market failure. Afog (talk) 11:44, 29 June 2009 (UTC)

(Sorry, didn't see this feedback at first since you didn't mention it in the edit summary) Okay. Let's compare the two scenarios. For there to be market failure, the number of people who by no CPU because of these compatibility problems must be higher than the number of people buying a CPU because of extensions that are superior because designers are not hampered by compatibility considerations. That this is the case seems far from obvious to me. Most people don't care about these extensions at all; those that do care tyically only whether their applications run better with them, and probably don't whether some other CPU that they're not going to buy also has it. --132.67.110.228 (talk) 14:54, 4 August 2009 (UTC)

You have a market failure if the sum of disadvantages to anybody is bigger than the sum of advantages to anybody else. The classical example is that a cheap but polluting production process is an advantage to the polluting factory but a disadvantage to his neighbors (who neither buy nor sell the product). In the case of CPUs, an incompatibility may give one company a short term advantage over its competitor, but it is a disadvantage to programmers and end users as well as to the competitor. Afog (talk) 15:11, 1 December 2009 (UTC)

vpmacswd

There's conflicting info about this instruction.

http://developer.amd.com/wordpress/media/2012/10/26568_APM_v41.pdf states it uses odd-numbered packed 16 bits integers from each source. But http://msdn.microsoft.com/en-us/library/vstudio/gg445175%28v=vs.100%29.aspx says even-numbered. Jamrial (talk) 09:06, 4 February 2014 (UTC)

Must be some off by one counting. I think the even indexed makes the most sense, and looking at http://support.amd.com/TechDocs/43479.pdf . The wording there is similar to the AMD tech manual, but it has a great illustration that seems to argue against it. So I guess odd numbered means odd ordered numbered, 1st, 3rd, aka index 0, 2. A classic computing confusion.Carewolf (talk) 20:36, 4 February 2014 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 2 external links on XOP instruction set. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive http://web.archive.org/web/20120229160805/http://software.intel.com/file/10069 to http://software.intel.com/file/10069
• Added archive http://web.archive.org/web/20140201175814/http://software.intel.com:80/en-us/file/319433-017pdf to http://software.intel.com/en-us/file/319433-017pdf

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 17:59, 20 July 2016 (UTC)