<?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  About the x64 stack Alignment in Intel® ISA Extensions</title>
    <link>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881087#M2501</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;this is due to a calling convention in x64 which requires the stack to be 16 bytes aligned before any call instruction. This is not (to my knwoledge) a hardware requirement but a software one. This provides a way to be sure that when entering a function (that is, after a call instruction), the value of the stack pointer is always 8 modulo 16. Thus permitting simple data alignement and storage/reads from aligned location in stack.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Matthieu&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 01 Mar 2010 09:00:17 GMT</pubDate>
    <dc:creator>matthieu_darbois</dc:creator>
    <dc:date>2010-03-01T09:00:17Z</dc:date>
    <item>
      <title>About the x64 stack Alignment</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881085#M2499</link>
      <description>&lt;P&gt;Hi all!&lt;/P&gt;
&lt;P&gt;I'm learning 64bit assembler,understand the x64 stack should be16-byte alignment, but I dont'tunderstandwhy?&lt;/P&gt;
&lt;P&gt;Thanksfor youranswers!&lt;/P&gt;</description>
      <pubDate>Sun, 28 Feb 2010 18:23:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881085#M2499</guid>
      <dc:creator>xfcyhuang</dc:creator>
      <dc:date>2010-02-28T18:23:35Z</dc:date>
    </item>
    <item>
      <title>About the x64 stack Alignment</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881086#M2500</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;Please correct me I am mistakten, but I guess that alignment stems from the time when cache lines in the caches where 16 bytes long. Having the stack aligned to 16 bytes as well provides a better alignment of the stack to the caches.&lt;/P&gt;
&lt;P&gt;Today, the cache line size is a multiple of 16 bytes.&lt;/P&gt;
&lt;P&gt;Oh, and with SSE, which uses 128bit registers, the 16-byte aligment is the most natural one, too.&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;-michael&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2010 07:35:23 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881086#M2500</guid>
      <dc:creator>Michael_K_Intel2</dc:creator>
      <dc:date>2010-03-01T07:35:23Z</dc:date>
    </item>
    <item>
      <title>About the x64 stack Alignment</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881087#M2501</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;this is due to a calling convention in x64 which requires the stack to be 16 bytes aligned before any call instruction. This is not (to my knwoledge) a hardware requirement but a software one. This provides a way to be sure that when entering a function (that is, after a call instruction), the value of the stack pointer is always 8 modulo 16. Thus permitting simple data alignement and storage/reads from aligned location in stack.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Matthieu&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2010 09:00:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881087#M2501</guid>
      <dc:creator>matthieu_darbois</dc:creator>
      <dc:date>2010-03-01T09:00:17Z</dc:date>
    </item>
    <item>
      <title>About the x64 stack Alignment</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881088#M2502</link>
      <description>&lt;P&gt;Thank you very much!&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2010 12:06:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881088#M2502</guid>
      <dc:creator>xfcyhuang</dc:creator>
      <dc:date>2010-03-01T12:06:06Z</dc:date>
    </item>
    <item>
      <title>About the x64 stack Alignment</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881089#M2503</link>
      <description>&lt;P&gt;In particular, 16-byte stack alignment avoids the need to insert conditional code to align SSE objects, both when allocating stack, and when entering SSE loops. This avoids the run-time failures seen on 32-bit systems when a gcc compiled function is called by one compiled by another compiler. Also, it avoids the alignment-dependent numerical differences incurred by differing loop alignment adjustments.&lt;/P&gt;
&lt;P&gt;32-bit linux in the past provided 8-byte alignment (pointers set to 8 modulo 16) so as to handle 64-bit objects efficiently. Certain 32-bit compilers for Windows "optimized" for varying alignment by avoiding the use of 64- and 128-bit moves.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2010 13:40:28 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881089#M2503</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2010-03-01T13:40:28Z</dc:date>
    </item>
    <item>
      <title>About the x64 stack Alignment</title>
      <link>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881090#M2504</link>
      <description>x64 compilers can assume the presence of SSE registers, which on Windows have a calling convention associated with them (XMM6-15 are nonvolatile, aka callee-save). By maintaining a known stack alignment at the entry of functions, the compiler can safely use the more efficientmovdqa to save the nonvolatile registers rather than using the unaligned movdqu version.</description>
      <pubDate>Fri, 05 Mar 2010 17:05:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-ISA-Extensions/About-the-x64-stack-Alignment/m-p/881090#M2504</guid>
      <dc:creator>neerajsi_msft</dc:creator>
      <dc:date>2010-03-05T17:05:45Z</dc:date>
    </item>
  </channel>
</rss>

