Comment #17 on issue 2513 by [email protected]: life benchmark slowness
http://code.google.com/p/v8/issues/detail?id=2513
I can confirm this is not a v8 regression, sorry, I must have tested wrong
before. The change is in the benchmark.
Adding |0 where you said does speed it up by 2x. But it is still 7x slower,
so something else seems to be the main issue here.
Regarding booleans and coercions, it seems like it is equally useful to
optimize bool|X as it is bool+X? Both coerce (to an int or to a number). I
understand that in "typical" JS it would be kind of odd to add a boolean to
a number, but the same is true for doing logical OR on a boolean. (And I
would argue that for compiled code, both are natural to do.)
In any case, this specific benchmark is persistently troublesome, I am not
sure why. We aren't seeing such issues on other codebases that I am aware
of (not on arewefastyet.com or in the emscripten benchmark suite).
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
