<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Bill,<div><br></div><div>Here are the numbers for SPEC.</div><div><br></div><div>I’ve measure 3 different configurations:</div><div>1. the compiler without the proposed patch (Reference)</div><div>2. the compiler with the proposed patch but global merge disabled on constants (i.e., default behavior after the patch applied)</div><div>3. the compiler with the proposed patch and global merge enabled on constants (i.e., with command line option global-merge-on-const).</div><div><br></div><div>I have attached 2 main comparisons: 1 vs 2 and 1 vs 3 (identify with ‘with_const’ for the latter).</div><div>This translates in 4 files because for each comparison I made a difference between the tests with a compilation error I hit (“cannot find [some system headers]”, these errors are the same between all the configurations) and the tests without.</div><div><br></div><div>SPEC_failsXXX report numbers with the sysroot include error.</div><div>SPECXXX report numbers without any errors.</div><div><br></div><div>On average, the default behavior of the compiler does not impact the compile time. When enabled, the constant processing has on average a negative impact of 2%.</div><div><br></div><div><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">-Quentin</div>
</div>
<div></div></div></body></html>