<?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 AVX alignment requirement in Intel® ISA Extensions</title>
    <link>https://community.intel.com/t5/Intel-ISA-Extensions/AVX-alignment-requirement/m-p/904143#M2811</link>
    <description>&lt;P&gt;Public statements imply no special alignment requirements for AVX, and that there will be no particular support for more than the 16-byte alignments supported in 64-bit OS. However, the vmovaps instruction requires 32-byte alignment, even though documents indicate there may be no significant advantage in using it. To avoid breaking applications where VECTOR ALIGNED directives/pragmas are used with Intel compilers, those directives would have to continue to require only 16-byte alignment.&lt;/P&gt;</description>
    <pubDate>Sun, 16 Nov 2008 00:00:26 GMT</pubDate>
    <dc:creator>TimP</dc:creator>
    <dc:date>2008-11-16T00:00:26Z</dc:date>
    <item>
      <title>AVX alignment requirement</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/AVX-alignment-requirement/m-p/904143#M2811</link>
      <description>&lt;P&gt;Public statements imply no special alignment requirements for AVX, and that there will be no particular support for more than the 16-byte alignments supported in 64-bit OS. However, the vmovaps instruction requires 32-byte alignment, even though documents indicate there may be no significant advantage in using it. To avoid breaking applications where VECTOR ALIGNED directives/pragmas are used with Intel compilers, those directives would have to continue to require only 16-byte alignment.&lt;/P&gt;</description>
      <pubDate>Sun, 16 Nov 2008 00:00:26 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/AVX-alignment-requirement/m-p/904143#M2811</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2008-11-16T00:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: AVX alignment requirement</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/AVX-alignment-requirement/m-p/904144#M2812</link>
      <description>&lt;DIV style="margin:0px;"&gt;Hi Tim18,&lt;/DIV&gt;
&lt;DIV style="margin:0px;"&gt;You are correct, 16-byte alignment is all that can be guaranteed in some contexts, although going forwardcompilers are encouraged to support 32-bit alignments where possible. There are significant performance advantages to being 32-byte aligned if you have 32-byte loads and stores, even for instructions that do not require alignment to behave correctly.&lt;/DIV&gt;
&lt;DIV style="margin:0px;"&gt;I won't advise anyone to use VMOVDQA ymm flavors - they #GP if not aligned: I have been burned too many times by this in production code. You may want to use them for checking alignment as a debug tool, but in shipping code it would be much safer to use VMOVDQU (or fused load/op) loads and stores.&lt;/DIV&gt;
&lt;DIV style="margin:0px;"&gt;Regards,&lt;/DIV&gt;
&lt;DIV style="margin:0px;"&gt;Mark&lt;BR /&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 26 Nov 2008 21:10:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/AVX-alignment-requirement/m-p/904144#M2812</guid>
      <dc:creator>Mark_B_Intel1</dc:creator>
      <dc:date>2008-11-26T21:10:37Z</dc:date>
    </item>
  </channel>
</rss>

