Chromium Code Reviews
Help | Chromium Project | Gerrit Changes | Sign in

Issue 2504263004: [crankshaft] No need to rely on the @@hasInstance protector. (Closed)

Can't Edit
Can't Publish+Mail
Start Review
11 months ago by Benedikt Meurer
11 months ago
Franzi, Yang
CC:, ofrobots
Target Ref:


[crankshaft] No need to rely on the @@hasInstance protector. In Crankshaft we can actually do an abstract interpretation of the @@hasInstance lookup when optimizing instanceof and then use the normal machinery to protect the result instead of relying on the global @@hasInstance protector cell for optimizations. This recovers the 100x performance drop in Node.js v7 reported in This patch should be easily back-mergable to Node.js v7. BUG=v8:5640, Committed: Cr-Commit-Position: refs/heads/master@{#41059}

Patch Set 1 #


Total messages: 13 (7 generated)
Benedikt Meurer
11 months ago (2016-11-17 06:02:25 UTC) #1
Benedikt Meurer
Yang: PTAL Franziska: FYI
11 months ago (2016-11-17 06:03:26 UTC) #4
On 2016/11/17 06:02:25, Benedikt Meurer wrote: lgtm.
11 months ago (2016-11-17 06:04:53 UTC) #5
commit-bot: I haz the power
CQ is trying da patch. Follow status at
11 months ago (2016-11-17 06:05:26 UTC) #9
commit-bot: I haz the power
Committed patchset #1 (id:1)
11 months ago (2016-11-17 06:39:37 UTC) #11
commit-bot: I haz the power
11 months ago (2016-11-17 22:37:30 UTC) #13
Message was sent while issue was closed.
Patchset 1 (id:??) landed as
Cr-Commit-Position: refs/heads/master@{#41059}
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld 81bcdb8aa