Bug 160441 - VM::topCallFrame should be a void* because it may not point to a CallFrame
Summary: VM::topCallFrame should be a void* because it may not point to a CallFrame
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 160438
Blocks:
  Show dependency tree / graph
 
Reported: 2016-08-01 20:52 PDT by Filip Pizlo
Modified: 2016-12-06 19:24 PST (History)
6 users (show)

See Also:

Attachments
Patch (1.13 KB, patch)
2016-12-06 15:07 PST, Karim 		mark.lam: review-
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Filip Pizlo 2016-08-01 20:52:14 PDT 
Patch forthcoming.
Comment 1 Karim 2016-12-06 15:07:09 PST 
Created attachment 296331 [details]
Patch
Comment 2 Mark Lam 2016-12-06 15:12:29 PST 
Comment on attachment 296331 [details]
Patch

I'm not sure that this is the right fix.  Is there any reason why we need to populate topCallFrame with topVMEntryFrame?
Comment 3 Mark Lam 2016-12-06 19:24:05 PST 
Comment on attachment 296331 [details]
Patch

r- because all the bots are red.  The patch fails to build.