<br><br><div class="gmail_quote">On Mon, Jul 23, 2012 at 4:39 PM, Armin Rigo <span dir="ltr"><<a href="mailto:arigo@tunes.org" target="_blank">arigo@tunes.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Brett,<br>
<div class="im"><br>
On Mon, Jul 23, 2012 at 10:15 PM, Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:<br>
> That's what I'm trying to establish; how much have they diverged and if I'm<br>
> looking in the proper place.<br>
<br>
</div>bm_mako.py is not from Unladen Swallow; that's why it is in<br>
pypy/benchmarks/own/. In case of doubts, check it in the history of<br>
Hg. The PyPy version was added from virhilo, which seems to be the<br>
name of his author, on 2010-12-21, and was not changed at all since<br>
then.<br></blockquote><div><br></div><div>OK. Maciej has always told me that a problem with the Unladen benchmarks was that some of them had artificial loop unrolling, etc., so I had assumed you had simply fixed those instances instead of creating entirely new benchmarks.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hg tells me that there was no change at all in the 'unladen_swallow'<br>
subdirectory, apart from 'unladen_swallow/perf.py' and adding some<br>
__init__.py somewhere. So at least these benchmarks did not receive<br>
any pypy-specific adapatations. If there are divergences, they come<br>
from changes done to the unladen-swallow benchmark suite after PyPy<br>
copied it on 2010-01-15.<br></blockquote><div><br></div><div>I know that directory wasn't changed, but I also noticed that some benchmarks had the same name, which is why I thought they were forked versions of the same-named Unladen benchmarks.</div>
<div><br></div><div>-Brett</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
A bientôt,<br>
<br>
Armin.<br>
</blockquote></div><br>