<?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 Thanks for the tip, Jim. So in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077886#M60530</link>
    <description>&lt;P&gt;Thanks for the tip, Jim. So if I use polymorphism to address this, I'd need to implement my own version of malloc that ends up allocating along the 64 bye boundary? How would I make it so that my malloc takes precendence over the standard malloc? Especially if I don't want to allocate everything to be algined?&amp;nbsp;&lt;/P&gt;

&lt;P&gt;If that's not an option then would I not just use mm_malloc?&lt;/P&gt;

&lt;P&gt;Also, do you have any insight as to why there is not compiler flag for this?&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 25 Jan 2017 13:52:04 GMT</pubDate>
    <dc:creator>Paulius_V_</dc:creator>
    <dc:date>2017-01-25T13:52:04Z</dc:date>
    <item>
      <title>KNL Fortran 64 byte alignment</title>
      <link>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077884#M60528</link>
      <description>&lt;P&gt;Hello all.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;I encountered an error after recompiling my code with -align array64byte and using !dir$ vector aligned directive.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;serial job &amp;nbsp;x86 - ok, mpi job x86 - ok , serial MIC - ok, MPI MIC - array index out of bounds.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;I suspect that this might be due to the MPI implementation using some C++ modules. Why is there no 64-byte alignment option in icc? Is there an easy way of addressing this issue through compiler flags? If not, and C++ alignment is indeed the cause of this failure then I can exclude such variables but this would be a labor intensive endeavour.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Any suggestions?&lt;/P&gt;

&lt;P&gt;Many thanks&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jan 2017 00:15:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077884#M60528</guid>
      <dc:creator>Paulius_V_</dc:creator>
      <dc:date>2017-01-24T00:15:40Z</dc:date>
    </item>
    <item>
      <title>Paulis,</title>
      <link>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077885#M60529</link>
      <description>&lt;P&gt;Paulis,&lt;/P&gt;

&lt;P&gt;Consider: overload new technique as well as overload malloc.&lt;/P&gt;

&lt;P&gt;See: &lt;A href="http://stackoverflow.com/questions/16270891/can-we-overload-malloc"&gt;http://stackoverflow.com/questions/16270891/can-we-overload-malloc&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Jim Dempsey&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jan 2017 15:35:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077885#M60529</guid>
      <dc:creator>jimdempseyatthecove</dc:creator>
      <dc:date>2017-01-24T15:35:09Z</dc:date>
    </item>
    <item>
      <title>Thanks for the tip, Jim. So</title>
      <link>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077886#M60530</link>
      <description>&lt;P&gt;Thanks for the tip, Jim. So if I use polymorphism to address this, I'd need to implement my own version of malloc that ends up allocating along the 64 bye boundary? How would I make it so that my malloc takes precendence over the standard malloc? Especially if I don't want to allocate everything to be algined?&amp;nbsp;&lt;/P&gt;

&lt;P&gt;If that's not an option then would I not just use mm_malloc?&lt;/P&gt;

&lt;P&gt;Also, do you have any insight as to why there is not compiler flag for this?&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2017 13:52:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077886#M60530</guid>
      <dc:creator>Paulius_V_</dc:creator>
      <dc:date>2017-01-25T13:52:04Z</dc:date>
    </item>
    <item>
      <title>Both Windows and Linux have</title>
      <link>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077887#M60531</link>
      <description>&lt;P&gt;Both Windows and Linux have an API to perform aligned allocation (you also have the Intel mm_malloc as you have shown). You only need to write a (a few) shell function(s) that receives the malloc/free arguments and makes the appropriate call the aligned variants (e.g. mm_malloc). You can do the same with the C++&amp;nbsp;new, [] new, delete, [] delete.&lt;/P&gt;

&lt;P&gt;Jim Dempsey&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2017 15:40:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077887#M60531</guid>
      <dc:creator>jimdempseyatthecove</dc:creator>
      <dc:date>2017-01-25T15:40:21Z</dc:date>
    </item>
    <item>
      <title>&gt;&gt; How would I make it so</title>
      <link>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077888#M60532</link>
      <description>&lt;P&gt;&amp;gt;&amp;gt;&amp;nbsp;How would I make it so that my malloc takes precendence over the standard malloc? Especially if I don't want to allocate everything to be aligned?&amp;nbsp;&lt;/P&gt;

&lt;P&gt;The two have contradictory objectives.&lt;/P&gt;

&lt;P&gt;Define your overload to suit your needs or use the alternate allocation/deallocation.&lt;/P&gt;

&lt;P&gt;Jim Dempsey&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2017 15:52:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/KNL-Fortran-64-byte-alignment/m-p/1077888#M60532</guid>
      <dc:creator>jimdempseyatthecove</dc:creator>
      <dc:date>2017-01-25T15:52:54Z</dc:date>
    </item>
  </channel>
</rss>

