<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 25.02.2019 19:16, Ondrej Pokorny
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4a26ba9c-9b2c-7e81-0af3-d62dd5379991@kluug.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 25.02.2019 18:12, J. Gareth
Moreton wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1927.1551114778@web-cluster.fastnet.co.uk">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<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</blockquote>
<p><br>
</p>
<p>Build Lazarus?</p>
</blockquote>
<p><br>
</p>
<p>What I meant: build compiler with and without your changes and
then compare build times for Lazarus. (So actually you compare the
compiler, just like Marco suggested.)<br>
</p>
<p><br>
</p>
<p>Ondrej<br>
</p>
</body>
</html>