Comment #52 on issue 2599 by redu...@gmail.com: Implement "use asm"
http://code.google.com/p/v8/issues/detail?id=2599
Hi guys, just reported issue #3080 , I'm not sure if it's related to this.
I understand that It's best to improve V8 as much as possible as priority
and I'm not going to argue with that.
My experience with asm.js in Chrome/V8 is that (unlike Firefox) it stalls a
lot, despite performance itself being fast. Unreal Citadel is pretty much a
static rendering demo where the CPU does little to nothing, and benchmarks
also use a finite and small number of code paths.
I've been trying to port a large game engine (linked above) that has 20mb
of asm.js code, and that probably stresses several more codepaths than
other tests, as it runs a custom physics engine, space grid hash
broadphase, GLES2 renderer, interpreted script, track-based animations,
particle systems, etc.
So the question is, isn't AOT instead of JIT compilation better for these
cases to avoid stalls? From what I understand reading the asm.js
specification is that it's not just an issue of optimization, but that it
should be much faster to parse and compile if properly detected, allowing
AOT for a smoother experience.
--
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
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
