Summary: | Accesses that are polymorphic on base but all share the same slot base in some shared prototype should use a hash set of structures for resolution | ||
---|---|---|---|
Product: | WebKit | Reporter: | Filip Pizlo <fpizlo> |
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | ||
Priority: | P2 | ||
Version: | WebKit Nightly Build | ||
Hardware: | All | ||
OS: | All |
Description
Filip Pizlo
2016-04-07 21:09:35 PDT
Something that I still need to check is whether those websites that take slow path on these megamorphic loads ends up sharing the same base structures across different static accesses. If they do, then this optimization is going to be great because as soon as an IC is repatched to use the hashtable, it will likely not need to take slow path. But if there's just a huge set of diverse structures that end up in these accesses then we need some other strategy. |