title: How should spec2017 set the compilation options?
body: <p>I am compiling my spec2017. In my <code>config</code> directory, there is an <code>Example-gcc-linux-x86.cfg</code> file.
  I copied it to a new file. I modified the <code>%define label</code> and <code>gcc</code> path.
  I also saw a <code>config</code> file used by others. I compared it. I found that its config file is somewhat different from mine.</p>
  <p>The main differences are:</p>
  <ol>
  <li><p>There is one more sentence in his config file than mine:</p>
  <p>strict_rundir_verify = 0</p>
  </li>
  <li><p>Its compilation options are different from mine.</p>
  </li>
  </ol>
  <p>his is:</p>
  <pre><code>default=base:         # flags for all base
     OPTIMIZE       = -g -O2 -static -march=native -fno-unsafe-math-optimizations  -fno-tree-loop-vectorize
  </code></pre>
  <p>mine is:</p>
  <pre><code>default=base:         # flags for all base
     OPTIMIZE       = -g -O3 -static -march=native -fno-unsafe-math-optimizations  -fno-tree-loop-vectorize
  </code></pre>
  <p>I mainly use spec2017 for prefetching experiments, may I ask</p>
  <ol>
  <li><p>What is the code that he added?</p>
  </li>
  <li><p>Which compile option is correct here?  If different compilation options are used between the papers, the results measured by spec2017 are not comparable? Then why these papers did not disclose the compilation rules of spec2017 they used?</p>
  </li>
  <li><p>Is it OK to compile spec2017 with the following command? Is it unnecessary to set up copies and threads in addition?</p>
  </li>
  </ol>
  <pre><code>runcpu --config=Example-gcc-linux-x86-test.cfg --reportable --action=run al
  </code></pre>
  <p>Thanks!</p>