Do not link in irtshim for SPEC perf benchmarks.  Otherwise code-growth in the IRT shim could make the compiler look like it has regressed.
Do not link in irtshim for SPEC perf benchmarks.  Otherwise code-growth
in the IRT shim could make the compiler look like it has regressed.

There is a separate issue: code-placement / link line drift.

The code generated by the unsandboxed translator does not see a
perf regression.  This is because the unsandboxed translator's
link line has been changed (and perhaps gets lucky with the
new code placement), but the baked in sandboxed translator's
commandline is linking in the shim earlier.  Thus we only see
the perf regression in one case, but not the other.

BUG= http://code.google.com/p/nativeclient/issues/detail?id=2715
TEST= run mesa with sandboxed vs unsandboxed translator, check timings

Review URL: https://chromiumcodereview.appspot.com/10005045

git-svn-id: 721b910a23eff8a86f00c8fd261a7587cddf18f8@8192 fcba33aa-ac0c-11dd-b9e7-8d5594d729c2

nacl-webkit/native_client,sbc100/native_client,sbc100/native_client,sbc100/native_client,sbc100/native_client,nacl-webkit/native_client,nacl-webkit/native_client,nacl-webkit/native_client,sbc100/native_client,nacl-webkit/native_client,sbc100/native_client