Bug 140804
| Summary: | If we inline a nested function call, we should be able to do GCSE on closure variable accesses and object allocation sinking on the activation | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Filip Pizlo <fpizlo> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Filip Pizlo
I'm pretty sure that this won't work right now because we don't reason about the activation that a NewFunction* operation references. But we totally should do this.
This would be a poor man's way of doing single-and-loving-it analysis: http://www.cs.purdue.edu/homes/suresh/papers/popl98.ps.gz
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Filip Pizlo
One outcome of this is that it would allow us to get rid of more TDZ checks, since we could reason about the TDZ locally.