<HTML>
<div><style> BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }</style>The compiler isn't a valid case because the input source is different (because of the very changes made to said compiler). It needs to be a project that doesn't share anything with the compiler (except the run-time libraries), so the source code is exactly the same so that when it is built, it runs the same no matter which version of the compiler it was built with.</div><div><br>
</div><div>I'm viewing it as a bit of a scientific experiment, where only a single variable is changed, namely the compiler used. The compiled program should produce exactly the same output and otherwise behave the same way, so that any time metrics reflect only how long it takes to complete and hence is reflective only of the quality of the machine code, not what the program is doing... if that makes any sense.<br>
</div><br>
Gareth aka. Kit<br>
<br>
<br>
<span style="font-weight: bold;">On Mon 25/02/19 18:08 , Marco van de Voort fpc@pascalprogramming.org sent:<br>
</span><blockquote style="BORDER-LEFT: #F5F5F5 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<br>
Op 2019-02-25 om 14:52 schreef J. Gareth Moreton:
<br>
<span style="color: rgb(102, 102, 102);">>
</span><br>
<span style="color: rgb(102, 102, 102);">> Given my recent work with the peephole optimizer, one thing that
</span><br>
<span style="color: rgb(102, 102, 102);">> sprung to mind is that I don't have a project that tests for
</span><br>
<span style="color: rgb(102, 102, 102);">> performance gains in a 'real world' program, where little
</span><br>
<span style="color: rgb(102, 102, 102);">> optimisations add up over time. Given that my x86-64 optimizer
</span><br>
<span style="color: rgb(102, 102, 102);">> overhaul is rather substantial and makes a lot of improvements when it
</span><br>
<span style="color: rgb(102, 102, 102);">> comes to conditional jumps and code efficiency, is there a benchmark
</span><br>
<span style="color: rgb(102, 102, 102);">> that could be used to show the performance improvement compared to the
</span><br>
<span style="color: rgb(102, 102, 102);">> trunk? There are small ones that test individual components, but
</span><br>
<span style="color: rgb(102, 102, 102);">> nothing substantially large that I'm aware of.
</span><br>
<span style="color: rgb(102, 102, 102);">>
</span><br>
<br>
Build the compiler?
<br>
<br>
_______________________________________________
<br>
fpc-devel maillist - <a href="mailto:fpc-devel@lists.freepascal.org">fpc-devel@lists.freepascal.org</a>
<br>
<a target="_blank" href="<a href="http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel">http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel</a>"><span style="color: red;">http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel</span></a>
<br>
<br>
<br>
</blockquote></HTML>