On 2015/09/01 16:03:18, wingo wrote:
LGTM, thanks for humoring my nitpicking, doing the perfect thing seems
impossible here.
Regarding desugaring: to my limited understanding there is no inlining
hazard;
TF will be able to do just as well with this desugaring as with indexed
arguments access. It seems to me that TF will have to support
arguments[n]
anyway, so I don't share Benedikt's concerns. This desugaring also
allows for
unrolling and load/store forwarding. Haven't poked TF at all yet though
so
I'm
sure Benedikt knows more there.
I think everyone is as happy with this CL as they're going to get. I'm
happy to
move things further in a follow-up, if anything else is needed. I'm also
fairly
confident that this will perform better than the current code which disables
optimization and misses out on clever allocation strategies, too. If there
are
any major problems, reverting is an option.
https://codereview.chromium.org/1272673003/
--
--
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/d/optout.
