RESOLVED FIXED216222
[JSC] Special property caching should check Structure's cacheability
https://bugs.webkit.org/show_bug.cgi?id=216222
Summary [JSC] Special property caching should check Structure's cacheability
Yusuke Suzuki
Reported 2020-09-05 22:12:01 PDT
[JSC] ModuleNamespaceObject's property caching has different mechanism than IC
Attachments
Patch (10.62 KB, patch)
2020-09-05 23:53 PDT, Yusuke Suzuki
no flags
Patch (10.49 KB, patch)
2020-09-06 00:02 PDT, Yusuke Suzuki
no flags
Patch (10.33 KB, patch)
2020-09-06 00:04 PDT, Yusuke Suzuki
saam: review+
Yusuke Suzuki
Comment 1 2020-09-05 23:53:02 PDT
Radar WebKit Bug Importer
Comment 2 2020-09-05 23:53:47 PDT
Yusuke Suzuki
Comment 3 2020-09-05 23:58:29 PDT
Comment on attachment 408116 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=408116&action=review > JSTests/stress/not-cache-over-uncacheable-dictionary.js:14 > +function shouldBe(actual, expected) { > + if (actual !== expected) > + throw new Error('bad value: ' + actual); > +} > + > +var object = {}; > +$vm.toUncacheableDictionary(object); > +shouldBe(String(object), `[object Object]`); > +shouldBe(String(object), `[object Object]`); > +shouldBe(String(object), `[object Object]`); > +object[Symbol.toStringTag] = "OK"; > +shouldBe(String(object), `[object OK]`); > +shouldBe(String(object), `[object OK]`); > +shouldBe(String(object), `[object OK]`); This test does not fail without this patch while we were caching. This is because we are relying on watchpoints for properties instead of structure ID. But in this patch, we changed the code not to cache properties in uncacheable-dictionary. So testing it here is nice.
Yusuke Suzuki
Comment 4 2020-09-06 00:02:34 PDT
Yusuke Suzuki
Comment 5 2020-09-06 00:04:16 PDT
Ryan Haddad
Comment 6 2020-09-07 22:33:19 PDT
*** Bug 216262 has been marked as a duplicate of this bug. ***
Saam Barati
Comment 7 2020-09-07 23:30:58 PDT
Comment on attachment 408118 [details] Patch r=me
Yusuke Suzuki
Comment 8 2020-09-08 00:21:15 PDT
Note You need to log in before you can comment on or make changes to this bug.