<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="XOP instruction set - Page 5 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=XOP_instruction_set&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=XOP_instruction_set&amp;p=6">3.Next</a>
</p>
<p>with the 3-byte VEX prefix.</p>

<p>Commentators have seen this as evidence that Intel has not allowed AMD to use any part of the large VEX coding space. AMD has been forced to use different codes in order to avoid using any code combination that Intel might possibly be using in its development pipeline for something else. The XOP coding scheme is as close to the VEX scheme as technically possible without risking that the AMD codes overlap with future Intel codes. This inference is speculative, since no public information is available about negotiations</p><p>
<a accesskey="1" href="page.php?w=XOP_instruction_set&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=XOP_instruction_set&amp;p=6">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
