Hi,
On Tue, Aug 16, 2011 at 8:43 AM, Maciej Fijalkowski wrote:
>> Is this something I should investigate on jit-short_from_state, or
>> could we consider it a separate problem and merge jit-short_from_state
>> anyway?
>
> Personally I would consider this a separate problem.
I agree. You can mer
On Mon, Aug 15, 2011 at 8:07 PM, Hakan Ardo wrote:
> Hi,
> I've been looking a bit at the go benchmark, which sometimes is
> significantly slower on jit-short_from_state.
>
> What's happening with default trace_limit=12000 on trunk is that the
> loop in random_playout is compiled into a loop conta
Hi,
I've been looking a bit at the go benchmark, which sometimes is
significantly slower on jit-short_from_state.
What's happening with default trace_limit=12000 on trunk is that the
loop in random_playout is compiled into a loop containing 209 guards
and the loop in computer_move is compiled into
