Comment #9 on issue 2734 by [email protected]: StringDictionary store is
very slow
http://code.google.com/p/v8/issues/detail?id=2734
Thanks for looking into this!
I am aware of semantical differences between Lua and JavaScript.
Regarding prototype chain check: I think it is fine if one has to rewrite
this with Object.create(null) or even new Map instead of {} to avoid
prototype check.
As for checking property details before storing: if they are checked inline
it should be a single comparison, property details are stored right next to
the value that we already loaded so in majority of cases they'll be in the
cache.
I think the biggest victory for LuaJIT2 here is not the absence of the
property details check but ability to version the loop for a completely
initialized state avoiding diamond like control flow inside the loop (this
comes naturally for a tracing JIT). Also IR allows it to eliminate
redundancies between loading and storing (e.g. calculations for
the "bucket" address).
--
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.
