<?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 Optimal GCC compile flags for 2nd gen i7 in Software Tuning, Performance Optimization &amp; Platform Monitoring</title>
    <link>https://community.intel.com/t5/Software-Tuning-Performance/Optimal-GCC-compile-flags-for-2nd-gen-i7/m-p/836504#M1146</link>
    <description>The Pentium4 native options are probably OK, if you want a 32-bit build. If you are able to get auto-vectorization at -O3, -march=pentium4 -mtune=barcelona will favor performance on CoreI7 while still running on Pentium4. Adding -msse4should help certain applications (e.g. complex data types), but won't run on Pentium4.&lt;BR /&gt;The -march=corei7 option of gcc 4.6 (replacing the pentium4 and barcelona options)is intended for the original Core I7 (still OK for I7-2). With gcc 4.5 on I7-2,you can use -mavx in place of -msse4and sometimes get an advantage. I expect 4.6 would get more out of -mavx.I've never tried -mavx for 32-bit compilation.</description>
    <pubDate>Thu, 01 Sep 2011 18:13:32 GMT</pubDate>
    <dc:creator>TimP</dc:creator>
    <dc:date>2011-09-01T18:13:32Z</dc:date>
    <item>
      <title>Optimal GCC compile flags for 2nd gen i7</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Optimal-GCC-compile-flags-for-2nd-gen-i7/m-p/836503#M1145</link>
      <description>Hello - Can anyone suggest optimal GCC compile flags (march, tune, sse, etc) for 2nd gen i7?&lt;BR /&gt;&lt;BR /&gt;I read GCC 4.6 adds support for -march=corei7, but I am using GCC 4.4 and 4.5. Also, I am cross compilng on a pentium4 host so -march=native may not be ideal. &lt;BR /&gt;&lt;BR /&gt;Any suggestions would be appreciated. &lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 01 Sep 2011 17:46:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Optimal-GCC-compile-flags-for-2nd-gen-i7/m-p/836503#M1145</guid>
      <dc:creator>jpburke</dc:creator>
      <dc:date>2011-09-01T17:46:05Z</dc:date>
    </item>
    <item>
      <title>Optimal GCC compile flags for 2nd gen i7</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Optimal-GCC-compile-flags-for-2nd-gen-i7/m-p/836504#M1146</link>
      <description>The Pentium4 native options are probably OK, if you want a 32-bit build. If you are able to get auto-vectorization at -O3, -march=pentium4 -mtune=barcelona will favor performance on CoreI7 while still running on Pentium4. Adding -msse4should help certain applications (e.g. complex data types), but won't run on Pentium4.&lt;BR /&gt;The -march=corei7 option of gcc 4.6 (replacing the pentium4 and barcelona options)is intended for the original Core I7 (still OK for I7-2). With gcc 4.5 on I7-2,you can use -mavx in place of -msse4and sometimes get an advantage. I expect 4.6 would get more out of -mavx.I've never tried -mavx for 32-bit compilation.</description>
      <pubDate>Thu, 01 Sep 2011 18:13:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Optimal-GCC-compile-flags-for-2nd-gen-i7/m-p/836504#M1146</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2011-09-01T18:13:32Z</dc:date>
    </item>
    <item>
      <title>Optimal GCC compile flags for 2nd gen i7</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Optimal-GCC-compile-flags-for-2nd-gen-i7/m-p/836505#M1147</link>
      <description>Recent gcc versions support -flto (link time optimization) which is said to work well with suitable applications.</description>
      <pubDate>Wed, 07 Sep 2011 16:12:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Optimal-GCC-compile-flags-for-2nd-gen-i7/m-p/836505#M1147</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2011-09-07T16:12:47Z</dc:date>
    </item>
  </channel>
</rss>

