<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Non-AVX opcodes in Intel® ISA Extensions</title>
    <link>https://community.intel.com/t5/Intel-ISA-Extensions/Non-AVX-opcodes/m-p/770259#M89</link>
    <description>It's more clear now ! Thank you for your reply.</description>
    <pubDate>Fri, 30 Jul 2010 17:53:10 GMT</pubDate>
    <dc:creator>aorl</dc:creator>
    <dc:date>2010-07-30T17:53:10Z</dc:date>
    <item>
      <title>Non-AVX opcodes</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/Non-AVX-opcodes/m-p/770257#M87</link>
      <description>Hi.&lt;BR /&gt;&lt;SPAN style="font-family: Verdana; font-size: xx-small;"&gt;&lt;SPAN style="font-family: Verdana; font-size: xx-small;"&gt;&lt;P&gt;I was just reading "Intel Advanced Vector Extensions Programming Reference" for the first time and a few questions popped up immediately after readingsection 4. Maybe some reader in this forum can help me out. &lt;BR /&gt;&lt;BR /&gt;1) does VEX prefix allow any type of prefix before it ? According to section 4.1.1, 4.1.2 and 4.1.3 I understand that no prefix is allowed, but figure 4-1 suggests the opposite&lt;BR /&gt;2) can I use the VEX prefix to encode an instruction like for example RDTSC (0F 31)?&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;/P&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;</description>
      <pubDate>Fri, 30 Jul 2010 16:12:28 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/Non-AVX-opcodes/m-p/770257#M87</guid>
      <dc:creator>aorl</dc:creator>
      <dc:date>2010-07-30T16:12:28Z</dc:date>
    </item>
    <item>
      <title>Non-AVX opcodes</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/Non-AVX-opcodes/m-p/770258#M88</link>
      <description>&lt;P&gt;The good thing about VEX encoding is that it has compacted the encoding and added the possibility of adding more opcodes. The usual SIMD perfixes 0F, 66, F2 F3 etc are encoded in 2nd or 3rd byte of the VEX. However when you decode those instructions these prefixes are present. You can not encode RDTSC with VEX. &lt;BR /&gt;VEX perfix is only valid for AVX instructions - SIMD instructions (encoded in VEX form).&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jul 2010 17:40:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/Non-AVX-opcodes/m-p/770258#M88</guid>
      <dc:creator>Brijender_B_Intel</dc:creator>
      <dc:date>2010-07-30T17:40:59Z</dc:date>
    </item>
    <item>
      <title>Non-AVX opcodes</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/Non-AVX-opcodes/m-p/770259#M89</link>
      <description>It's more clear now ! Thank you for your reply.</description>
      <pubDate>Fri, 30 Jul 2010 17:53:10 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/Non-AVX-opcodes/m-p/770259#M89</guid>
      <dc:creator>aorl</dc:creator>
      <dc:date>2010-07-30T17:53:10Z</dc:date>
    </item>
    <item>
      <title>Non-AVX opcodes</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/Non-AVX-opcodes/m-p/770260#M90</link>
      <description>It looks like prefixes from "group1" (Lock and Repeat prefixes) is not allowed. Prefixes from "group2" (Segment overrides) are allowed and Operand size overridenot allowed but address size override (0x67) is.&lt;BR /&gt;&lt;BR /&gt;Knut</description>
      <pubDate>Sat, 07 Aug 2010 16:42:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/Non-AVX-opcodes/m-p/770260#M90</guid>
      <dc:creator>knujohn4</dc:creator>
      <dc:date>2010-08-07T16:42:35Z</dc:date>
    </item>
  </channel>
</rss>

