Comment #7 on issue 4400 by ad...@chromium.org: Default parameters segfault
when lazily parsed
https://code.google.com/p/v8/issues/detail?id=4400
The only problem with the solution in #6 is that it inflates the
materialized literal count. I've filed issue 4407 to track that problem
(which
Updates:
Status: Started
Comment #6 on issue 4400 by ad...@chromium.org: Default parameters segfault
when lazily parsed
https://code.google.com/p/v8/issues/detail?id=4400
No, this is much simpler to fix, just need to pull the literals count out
of the function_state_ and copy it dow
Updates:
Status: Assigned
Owner: ad...@chromium.org
Comment #5 on issue 4400 by ad...@chromium.org: Default parameters segfault
when lazily parsed
https://code.google.com/p/v8/issues/detail?id=4400
This is pretty straightforwardly-broken:
ParseArrayLiteral/ParseObjectLiteral
Issue 4400: Default parameters segfault when lazily parsed
https://code.google.com/p/v8/issues/detail?id=4400
This issue is now blocking issue v8:2160.
See https://code.google.com/p/v8/issues/detail?id=2160
--
You received this message because you are listed in the owner
or CC fields of this iss
Updates:
Cc: ad...@chromium.org
Comment #3 on issue 4400 by ad...@chromium.org: Default parameters segfault
when lazily parsed
https://code.google.com/p/v8/issues/detail?id=4400
(No comment was entered for this change.)
--
You received this message because this project is configured
Updates:
Status: Available
Owner: ---
Cc: caitpott...@gmail.com rossb...@chromium.org
Comment #2 on issue 4400 by caitpott...@gmail.com: Default parameters
segfault when lazily parsed
https://code.google.com/p/v8/issues/detail?id=4400
(No comment was entered for this c
Comment #1 on issue 4400 by caitpott...@gmail.com: Default parameters
segfault when lazily parsed
https://code.google.com/p/v8/issues/detail?id=4400
This is slightly more complicated for the default parameters case, because
the parser doesn't incorporate these literals into the formal mater
